refactor(frontend): extract rule pre-content processing logic into independent module
docs: update documentation for error handling and log desensitization
test: add unit tests for log desensitization and rule pre-content
- Refactored the error handling in the data connector to classify and raise errors using a shared classifier, improving maintainability.
- Updated the `classify_and_raise_connector_error` function to include operation context for better logging and error tracking.
- Introduced structured error responses for connection failures, including detailed error codes and messages.
- Enhanced API error responses to include a request ID for better traceability in error handling.
- Updated frontend components to handle new error structures and display relevant messages to users.
- Added tests to ensure proper error classification and response handling across various scenarios.
- Updated error handling across various components to ensure all application-controlled errors return HTTP 200 with a structured error format.
- Introduced a unified protocol for both non-streaming and streaming APIs, specifying response formats for success and error scenarios.
- Removed legacy response formats and unnecessary fields, such as `token`, from error responses.
- Enhanced documentation to reflect the new error handling strategy and response structures.
- Added new error codes and improved handling for specific error scenarios, including storage full conditions.
Adjust the backend error handling protocol to uniformly return HTTP 200 status code for all application control errors, with error information identified through the status field in the response body. Modified error handlers, route handling logic, and related test cases to ensure the frontend can correctly handle error responses.
- Modify error_handler.py global error handler to always return HTTP 200
- Update all route handling logic, remove explicit HTTP error status codes
- Adjust test cases to verify the new error handling protocol
- Update frontend apiClient.ts to handle error responses for streaming requests
- Improve related documentation explaining the new error handling specifications
- Add unified error handling protocol for frontend and backend
- Add error code mapping and internationalization (i18n) support
- Implement global error handlers and frontend error handling utilities
- Update existing code to use the new error handling approach
- Add error handling related test cases
- Improve error handling documentation and specifications
Chenglong Wang
y-agent-ai
zhb-ai