-
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
Add metadata to data being sent to API endpoint in json dump registration backend #5053
Conversation
047a0c9
to
54efef5
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #5053 +/- ##
=======================================
Coverage 96.72% 96.73%
=======================================
Files 770 771 +1
Lines 26534 26588 +54
Branches 3452 3458 +6
=======================================
+ Hits 25666 25720 +54
Misses 606 606
Partials 262 262 ☔ View full report in Codecov by Sentry. |
54efef5
to
8f487bf
Compare
Few design considerations: Tried making the To show all metadata variables (additional and required) in the metadata selection box, and grey out all variables which are required by default, thought about adding the registration variables to the |
205d6aa
to
5a5e6a8
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, I think it's mostly polishing from here on :)
src/openforms/js/components/admin/form_design/registrations/json_dump/JSONDumpOptionsForm.js
Outdated
Show resolved
Hide resolved
5a5e6a8
to
a191924
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.
Neat!
One more thing that caught my attention in storybook is that your help texts for the form fields don't end with a <kbd>.</kbd>
, which looks odd and is inconsistent with (most of) the other form fields.
So, form label can be without, help text/tooltip should be with period as they are typically actual sentences (or should be!).
...penforms/js/components/admin/form_design/registrations/json_dump/fields/MetadataVariables.js
Outdated
Show resolved
Hide resolved
53eacd6
to
d81405f
Compare
...penforms/js/components/admin/form_design/registrations/json_dump/fields/MetadataVariables.js
Outdated
Show resolved
Hide resolved
d81405f
to
857c799
Compare
Also add support for an extra static variables registry in generate_json_schema
If there is no authentication, the value can be an empty string
If there is no content (in case of an HTTP 204 response for example), converting the response to json results in an error, so we just return an empty string
* Improve UX by introducing a (collapsed) fieldset which contains a table of fixed variables, and a variable selection box to add additional variables. * Fix imports * Add TODO: currently, this is tricky because the form registration options are saved before the (user defined) form variables are persisted. If this field is limited to static/registration variables, however, it will be possible as they are defined in the code. At this point in time, though, not sure how strict we should make this. * Fix help texts of JSON dump option fields. They are sentences that should end with a period
857c799
to
377bd53
Compare
377bd53
to
58b6492
Compare
Closes #5012
Changes
Add metadata to data being sent to API endpoint in JSON dump registration backend
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
Dockerfile/scripts
./bin
folderCommit hygiene