Description:
This PR refactors the error handling logic in several components by introducing the ErrorConsumer utility. The main goal is to streamline and standardize how errors are consumed and displayed across the application. This change replaces the previous usage of splitErrorsByPath and direct error handling within the components.
Out of Scope:
Any additional functionality or refactoring beyond error handling and the specific components mentioned.
Screenshots:
(Not applicable for this PR)
Describe any introduced user-facing changes:
Users may notice a more consistent and possibly improved error messaging experience when interacting with the affected forms.
Describe any introduced API changes:
No API changes are introduced with this PR. The changes are internal to the application’s frontend error handling logic.
Additional Info:
The new ErrorConsumer utility provides a centralized way to handle and consume errors, potentially making future error handling and debugging easier.
The affected components now utilize useErrorConsumer for error handling, ensuring consistency across different parts of the application.
mastercactapus
commented
6 days ago
Description: This PR refactors the error handling logic in several components by introducing the
ErrorConsumerutility. The main goal is to streamline and standardize how errors are consumed and displayed across the application. This change replaces the previous usage ofsplitErrorsByPathand direct error handling within the components.Out of Scope:
Screenshots: (Not applicable for this PR)
Describe any introduced user-facing changes:
Describe any introduced API changes:
Additional Info:
ErrorConsumerutility provides a centralized way to handle and consume errors, potentially making future error handling and debugging easier.useErrorConsumerfor error handling, ensuring consistency across different parts of the application.