-
Notifications
You must be signed in to change notification settings - Fork 192
Modal for global error handling should be moved to "ketcher-react" #2922
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
chgayane
added a commit
that referenced
this issue
Dec 18, 2023
chgayane
added a commit
that referenced
this issue
Dec 18, 2023
9 tasks
chgayane
added a commit
that referenced
this issue
Dec 25, 2023
chgayane
added a commit
that referenced
this issue
Dec 26, 2023
chgayane
added a commit
that referenced
this issue
Dec 27, 2023
chgayane
added a commit
that referenced
this issue
Dec 27, 2023
chgayane
added a commit
that referenced
this issue
Jan 4, 2024
chgayane
added a commit
that referenced
this issue
Jan 5, 2024
chgayane
added a commit
that referenced
this issue
Jan 5, 2024
chgayane
added a commit
that referenced
this issue
Jan 5, 2024
chgayane
added a commit
that referenced
this issue
Jan 5, 2024
chgayane
added a commit
that referenced
this issue
Jan 8, 2024
chgayane
added a commit
that referenced
this issue
Jan 15, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Background
Global error handling was added in PR 730. With this implementation errorHandler triggers Modal on the client / demo application which is not a reliable approach (as for example, revealed in bug 2790)
Solution
For fixing bug 2790 the Info / Error modal was moved to "ketcher-react" (PR 2868). Triggering of modal for all other errors handled in PR 730 should be also moved to "ketcher-react". In this case the client does not need to import the InfoModal component and take care about this error handling.
Additional context
The text displayed in the modal for other errors has to be verified / discussed.
The text was updated successfully, but these errors were encountered: