Neo API and Conversation Management Refactoring #814
Conversation
… Neo API - Changed the 'Table' field to 'Prefix' in the Setting struct to better represent its purpose as a table name prefix. - Updated all relevant instances in the codebase to use the new 'Prefix' field, ensuring consistency across the application. - Adjusted logging and table retrieval methods to reflect the new naming convention, enhancing clarity and maintainability.
- Introduced new methods for initializing RAG and store, improving modularity and clarity in the Load function. - Refactored the assistant initialization process to streamline the loading of built-in assistants and set RAG configurations. - Moved the defaultAssistant method from neo.go to load.go for better organization and accessibility. - Enhanced error handling in store initialization to support multiple connector types, including Redis and Mongo. - Updated the assistant struct to include RAG settings, improving the overall assistant management capabilities.
- Deleted the assistant.go and assistant_test.go files, which contained the implementation and tests for assistant management. - This cleanup reduces complexity and focuses on core functionalities, paving the way for future enhancements in assistant handling.
- Updated the SetRAG function to include RAG settings, allowing for more detailed configuration during assistant initialization. - Refactored the LoadBuiltIn function to streamline the saving process of assistants, improving error handling and code clarity. - Modified loadPrompts and loadScript functions to return timestamps, enabling tracking of creation and update times for assistants. - Enhanced the Assistant struct with created_at and updated_at fields, improving data management and traceability. - Overall improvements to the assistant loading process, ensuring better organization and maintainability of the codebase.
|
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: 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: 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: 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. |
|
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: 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: 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: SQLite3 redis: 6 mongo: 6.0 test workflow is running, the results of the run will be commented later. |
|
✨DONE✨ db: MySQL5.7 redis: 4 mongo: 6.0 passed. |
|
✨DONE✨ db: MySQL5.7 redis: 6 mongo: 6.0 passed. |
|
✨DONE✨ db: MySQL5.7 redis: 5 mongo: 6.0 passed. |
|
✨DONE✨ db: MySQL8.0 redis: 4 mongo: 6.0 passed. |
|
✨DONE✨ db: MySQL8.0 redis: 5 mongo: 6.0 passed. |
|
✨DONE✨ db: MySQL8.0 redis: 6 mongo: 6.0 passed. |
|
✨DONE✨ db: SQLite3 redis: 5 mongo: 6.0 passed. |
|
✨DONE✨ db: SQLite3 redis: 6 mongo: 6.0 passed. |
|
✨DONE✨ db: SQLite3 redis: 4 mongo: 6.0 passed. |
Changes