-
Notifications
You must be signed in to change notification settings - Fork 1
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-zaak/open-notificaties#156] Several changes to Kanalen #14
Conversation
30bb60b
to
68c8ba8
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #14 +/- ##
==========================================
- Coverage 89.23% 89.21% -0.03%
==========================================
Files 29 29
Lines 604 612 +8
==========================================
+ Hits 539 546 +7
- Misses 65 66 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
3d1f4b7
to
dfce6ea
Compare
410e968
to
d0ea73e
Compare
64885ff
to
a1caa4c
Compare
@stevenbal see if you can revisit this PR next week now that open-zaak/open-zaak#1800 has been completed |
741e8d9
to
99e77b4
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.
Support nested fields on kanaal kenmerken
I guess this is suppose the extra_kwargs[kenmerk_1][field_name]
and is for supporting stuff added in open zaak rather than here?
Have some comments and I do not think the nested fields are actually tested or at least the help text
notifications_api_common/kanalen.py
Outdated
self, | ||
obj: Model, | ||
data: Union[Dict, None] = None, | ||
request: Union[Request, None] = None, # noqa |
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.
What does this request do?
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.
Could this just not be in data?
edit: actually probably not
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.
Actually again this is something fore open zaak?
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.
You're right, this is necessary for Open Zaak to create the URLs: https://github.com/open-zaak/open-zaak/pull/1757/files#diff-b74ad95db3a00961f14403f57ab65597401cc8b8b1ef88e162d3214c4baf70d6R54.
data
is the actual request data (JSON) that is posted, so it can't really be a part of that I think
that's right, I've added the help_text stuff to be able to mark the help text for |
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.
Yep, looks good.
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
90b3d3d
to
1a0cd10
Compare
…et_kenmerken and add hook for `_get_field` to support nested attributes in Open Zaak
this command was previously part of commonground-api-common, but removed
1a0cd10
to
48b9571
Compare
Related issue: open-zaak/open-notificaties#156
Requires zgw-consumers to be upgraded in Open Zaak
Changes: