-
Notifications
You must be signed in to change notification settings - Fork 6
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
✨ [open-formulieren/open-forms#5033] User friendly error in case of 503 #783
✨ [open-formulieren/open-forms#5033] User friendly error in case of 503 #783
Conversation
Bundle ReportChanges will increase total bundle size by 742 bytes (0.01%) ⬆️. This is within the configured threshold ✅ Detailed changes
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #783 +/- ##
==========================================
+ Coverage 83.41% 83.62% +0.20%
==========================================
Files 240 241 +1
Lines 4752 4757 +5
Branches 1275 1268 -7
==========================================
+ Hits 3964 3978 +14
+ Misses 754 745 -9
Partials 34 34
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
bd62356
to
c0ca478
Compare
c0ca478
to
7476012
Compare
7476012
to
8dac57e
Compare
Not sure why exactly this is or isn't working properly with the built in decorator, but I suspect it has something to do with the error boundary of react router itself/the decorator and the error state not being reset properly when the story remounts. The workaround just creates a new memory router instance on every render of the story, discarding any router state between every story render which seems to solve the problem.
8dac57e
to
0217758
Compare
Closes open-formulieren/open-forms#5033