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
Additional context
I faced this problem by using a minimal Redoc HTML file, initializing Redoc manually. If the spec URL is wrong, I get a stack trace, and the component dies.
I'd like to be able to re-init the component with the right URL (I'm using a select to switch specs).
I think the issue is because of an uncaught error in a promise, preventing (or better said, not triggring) the callback execution.
Maybe this is related to #1686, or #690 (similar behavior, but different cause).
The text was updated successfully, but these errors were encountered:
Describe the bug
Error callback not called if specs are not found.
Expected behavior
The error callback being called even in this case, so to be able to recover.
Minimal reproducible OpenAPI snippet(if possible)
N/A
Screenshots
Additional context
I faced this problem by using a minimal Redoc HTML file, initializing Redoc manually. If the spec URL is wrong, I get a stack trace, and the component dies.
I'd like to be able to re-init the component with the right URL (I'm using a select to switch specs).
I think the issue is because of an uncaught error in a promise, preventing (or better said, not triggring) the callback execution.
Maybe this is related to #1686, or #690 (similar behavior, but different cause).
The text was updated successfully, but these errors were encountered: