You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Task Description
We are currently using a temporary any type for handling Apollo Client network errors in the getNormalizedError function. This is due to the incomplete error handling and typing implementation for the various error types we can receive from Apollo Client.
To ensure better type safety and maintainable code, we need to properly handle and type all possible errors from Apollo Client. This task is focused on implementing a robust error handling strategy with appropriate types for all Apollo Client errors.
Sub-tasks
Investigate the types of errors that Apollo Client can throw (e.g., ServerError, NetworkError, etc.).
Define and implement proper types for network and GraphQL errors from Apollo Client.
Replace the any type in getNormalizedError with the appropriate types.
Test the error handling with various Apollo Client error scenarios (e.g., network errors, GraphQL validation errors, etc.).
Update documentation and comments regarding the new error handling approach.
Related Issues
Link to related issues or tasks, if any.
Additional Context
Add any other context or information here.
The text was updated successfully, but these errors were encountered:
Task Description
We are currently using a temporary any type for handling Apollo Client network errors in the getNormalizedError function. This is due to the incomplete error handling and typing implementation for the various error types we can receive from Apollo Client.
To ensure better type safety and maintainable code, we need to properly handle and type all possible errors from Apollo Client. This task is focused on implementing a robust error handling strategy with appropriate types for all Apollo Client errors.
Sub-tasks
Related Issues
Link to related issues or tasks, if any.
Additional Context
Add any other context or information here.
The text was updated successfully, but these errors were encountered: