-
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
Implement Objects API sets #4332
Conversation
Mostly taken from #3146
75c8cf2
to
6d16c82
Compare
Implementation mostly taken from the ZGW set PR
…ersions fetching They now take a new query parameter, specifiying the group to use. Tests are updated.
6d16c82
to
2aa1be4
Compare
Tests still need to be added to check that an explicitly provided group is being used.
It is assumed that the ZGW registration will use the default Objects API. This is currently not configurable, but might be in the future.
It now takes a new `objects_api_group` parameter, similar to zgw. `registration_backend` is now made required, as it doesn't really make sense to have it optional. Tests were adapted/refactored.
2aa1be4
to
ddb427e
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #4332 +/- ##
==========================================
- Coverage 96.25% 96.24% -0.02%
==========================================
Files 731 731
Lines 23741 23789 +48
Branches 2800 2807 +7
==========================================
+ Hits 22853 22895 +42
- Misses 617 620 +3
- Partials 271 274 +3 ☔ View full report in Codecov by Sentry. |
objects_api_config = ObjectsAPIConfig.get_solo() | ||
assert isinstance(objects_api_config, ObjectsAPIConfig) |
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.
I assumed we use the default objects API group when registering to the Objects API from the ZGW registration.
Should we add support for group selection as well for ZGW?
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.
Yeah, selection seems best and consistent, but this can be a separate PR
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.
Opened #4344
src/openforms/js/components/admin/form_design/registrations/objectsapi/LegacyConfigFields.js
Show resolved
Hide resolved
src/openforms/js/components/admin/form_design/registrations/objectsapi/V2ConfigFields.js
Show resolved
Hide resolved
src/openforms/js/components/admin/form_design/registrations/objectsapi/hooks.js
Show resolved
Hide resolved
src/openforms/js/components/admin/form_design/registrations/objectsapi/utils.js
Show resolved
Hide resolved
src/openforms/registrations/contrib/objects_api/migrations/0017_move_singleton_data.py
Show resolved
Hide resolved
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.
this can be dropped entirely - and the zgw config/api group should get the same treatment.
Closing to declutter :) |
For #4267
Changes
This is best reviewed commit per commit.
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.sh
./bin/compilemessages_js.sh
Commit hygiene