Enhance Neo API assistant message storage and structure #820
Enhance Neo API assistant message storage and structure #820trheyi merged 2 commits intoYaoApp:mainfrom
Conversation
- Removed unused utility imports and streamlined the saveChatHistory method to improve message storage efficiency. - Updated the Message struct to include new fields for assistant identification and mentions, enhancing message context and traceability. - Modified the history table structure to accommodate new assistant-related fields and mentions, ensuring comprehensive data storage. - Improved the SaveHistory method to process and store mentions alongside messages, providing better context for user interactions. These changes enhance the robustness and maintainability of the Neo API, paving the way for improved message handling and assistant functionalities.
- Added nil checks for response objects in the Execute method to prevent potential nil pointer dereferences. - Updated the streamChat method to include assistant identification details (ID, name, avatar) in the message structure, improving context for messages. - Introduced a new field in the Message struct to mark messages as new, enhancing message tracking capabilities. These changes improve the robustness and maintainability of the Neo API, paving the way for better message handling and assistant functionalities.
|
Thank you for the PR! The db: SQLite3 redis: 4 mongo: 6.0 test workflow is running, the results of the run will be commented later. |
|
Thank you for the PR! The db: MySQL5.7 redis: 6 mongo: 6.0 test workflow is running, the results of the run will be commented later. |
|
Thank you for the PR! The db: SQLite3 redis: 6 mongo: 6.0 test workflow is running, the results of the run will be commented later. |
|
Thank you for the PR! The db: MySQL5.7 redis: 4 mongo: 6.0 test workflow is running, the results of the run will be commented later. |
|
Thank you for the PR! The db: SQLite3 redis: 5 mongo: 6.0 test workflow is running, the results of the run will be commented later. |
|
Thank you for the PR! The db: MySQL8.0 redis: 6 mongo: 6.0 test workflow is running, the results of the run will be commented later. |
|
Thank you for the PR! The db: MySQL8.0 redis: 5 mongo: 6.0 test workflow is running, the results of the run will be commented later. |
|
Thank you for the PR! The db: MySQL5.7 redis: 5 mongo: 6.0 test workflow is running, the results of the run will be commented later. |
|
Thank you for the PR! The db: MySQL8.0 redis: 4 mongo: 6.0 test workflow is running, the results of the run will be commented later. |
|
✨DONE✨ db: SQLite3 redis: 6 mongo: 6.0 passed. |
|
✨DONE✨ db: SQLite3 redis: 4 mongo: 6.0 passed. |
|
✨DONE✨ db: MySQL5.7 redis: 6 mongo: 6.0 passed. |
|
✨DONE✨ db: MySQL5.7 redis: 4 mongo: 6.0 passed. |
|
✨DONE✨ db: MySQL5.7 redis: 5 mongo: 6.0 passed. |
|
✨DONE✨ db: SQLite3 redis: 5 mongo: 6.0 passed. |
|
✨DONE✨ db: MySQL8.0 redis: 4 mongo: 6.0 passed. |
|
✨DONE✨ db: MySQL8.0 redis: 6 mongo: 6.0 passed. |
|
✨DONE✨ db: MySQL8.0 redis: 5 mongo: 6.0 passed. |
1 participant
These changes enhance the robustness and maintainability of the Neo API, paving the way for improved message handling and assistant functionalities.