👽 Update NotificationsConfig client usage #37
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
notifications-api-common has changed its underlying client to ape_pie.APIClient due to a zgw-consumers update (maykinmedia/notifications-api-common#15)
Closed
1 task
added 10 commits
October 24, 2024 11:51
To make them match with notifications-api-common>=0.3.0
|
@stevenbal I can't add you as a reviewer, probably because you made this PR, so i'll create a new PR for this branch |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
notifications-api-common has changed its underlying client to ape_pie.APIClient due to a zgw-consumers update
required after maykinmedia/notifications-api-common#15
TODO: