-
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
ZGW UX improvements: select document type #4817
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #4817 +/- ##
=======================================
Coverage 96.60% 96.61%
=======================================
Files 749 749
Lines 25563 25616 +53
Branches 3383 3394 +11
=======================================
+ Hits 24696 24749 +53
Misses 604 604
Partials 263 263 ☔ View full report in Codecov by Sentry. 🚨 Try these New Features:
|
d340a4a
to
46e83b5
Compare
46e83b5
to
0671396
Compare
2cd5e88
to
b485b81
Compare
7ba5eca
to
ab76ea3
Compare
I was wondering, if you still wanted to change the |
src/openforms/js/components/admin/form_design/registrations/zgw/ZGWOptionsForm.js
Show resolved
Hide resolved
Yes, but I'll do that when I get to the medewerker roltype field, since that probably also requires it! So out of scope for this PR, in scope for the next one. |
Once a case type is selected, the available document type options are fetched from the backend and we only store the 'description' field value in the configuration options.
Added the serializer option to specify a document type via its description, rather than having to provide a fully qualified URL.
The serializer that produces the available document types is now properly in English, to be consistent with the rest of the serializers. This requires an update to the formio-builder too.
Replaced endpoints with their English variant for consistency.
Tests broke due to changes in behaviour, but the assertions were not updated accordingly yet.
The specified document type is now dynamically resolved within the case type of the created case, using the submissions completion time to determine the correct version to use. The legacy configuration options now emit deprecation warnings, but will still be supported for the foreseeable future.
* Added missing prop type for new form field * Extended list of field names contained in optional settings fieldset
Consistenly use 'document types' rather than informatieobjecttypen, as the URLs themselves have been updated and new code uses this language.
ab76ea3
to
fe771da
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.
Looks good to me 👍
src/openforms/js/components/admin/form_design/registrations/zgw/ZGWOptionsForm.js
Show resolved
Hide resolved
@@ -370,8 +395,8 @@ def _validate_catalogue_case_and_doc_type( | |||
) | |||
err_invalid_document_type = ErrorDetail( | |||
_( | |||
"The provided informatieobjecttype does not exist in the specified " | |||
"selected case type or Catalogi API." | |||
"The provided informatieobjecttype does not exist in the selected case " |
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.
"The provided informatieobjecttype does not exist in the selected case " | |
"The provided document type does not exist in the selected case " |
Closes #4606 (partially
TODO
Changes
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