-
Notifications
You must be signed in to change notification settings - Fork 26
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
Feature/4798 custom confirmation modal #4814
Feature/4798 custom confirmation modal #4814
Conversation
3e198d4
to
4aaa7cc
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #4814 +/- ##
=======================================
Coverage 96.57% 96.57%
=======================================
Files 748 748
Lines 25448 25448
Branches 3369 3369
=======================================
Hits 24576 24576
Misses 608 608
Partials 264 264 ☔ View full report in Codecov by Sentry. |
@robinmolen can you fix the merge conflicts? Also not sure if the failing tests are related to the code changes? |
e1881c9
to
231063c
Compare
There is a new window.confirm added in a recent commit, in the |
231063c
to
9dbb416
Compare
I've replaced the |
src/openforms/js/components/admin/form_design/registrations/zgw/fields/ZGWAPIGroup.js
Outdated
Show resolved
Hide resolved
c5b04b4
to
3c47cb5
Compare
Rendering a component inside a hook has some serious performance impacts. To prevent this, the useConfirm now returns the needed props and a reference to the confirmationModal component. For more info: #4814 (comment)
Rendering a component inside a hook has some serious performance impacts. To prevent this, the useConfirm now returns the needed props and a reference to the confirmationModal component. For more info: #4814 (comment)
477649e
to
115e00e
Compare
Rendering a component inside a hook has some serious performance impacts. To prevent this, the useConfirm now returns the needed props and a reference to the confirmationModal component. For more info: #4814 (comment)
115e00e
to
d7217e1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Holding of a little longer because of the SDK context/decorator for storybook I mentioned on Slack. I think it would clean up the new/updated interaction tests, and I'm curious if that formik onChange stuff is still necessary, since what it currently does is stop tracking the isTouched
state and once we refactor to not roll our validation errors/mechanics 100% on our own, that will definitely cause some problems then :)
d7217e1
to
720701a
Compare
Rendering a component inside a hook has some serious performance impacts. To prevent this, the useConfirm now returns the needed props and a reference to the confirmationModal component. For more info: #4814 (comment)
Replaced window dialog handling with new dialog react modal handling
Rendering a component inside a hook has some serious performance impacts. To prevent this, the useConfirm now returns the needed props and a reference to the confirmationModal component. For more info: #4814 (comment)
720701a
to
022d950
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
bellissimo
Closes #4798
Changes
Replacing all
window.confirm(...)
confirmations with a new custom React hook (useConfirm
). This new hook is using our Modal component to display the confirmation message. These changes happend to keep the application UI uniform.Checklist
Check off the items that are completed or not relevant.
Impact on features
Release management
I have updated the translations assets (you do NOT need to provide translations)
./bin/makemessages_js.sh
./bin/compilemessages_js.sh
Commit hygiene