🚧 [maykinmedia/django-setup-configuration#16] Setup config fixes #193
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
|
The |
ensure that notificaties API can access itself, to complete the configuration
and remove gemma-zds-client
stevenbal
force-pushed
the
issue/setup-config-missing-nrc-config
branch
from
99df438 to
68da993
Compare
This was referenced Dec 6, 2024
|
This has been fixed in the PR that implements a step to load subscriptions with the refactored setup configuration command: #209 |
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.
Fixes: maykinmedia/django-setup-configuration#16
reliant on maykinmedia/notifications-api-common#15 to verify if view-config is correct and maykinmedia/commonground-api-common#37
TODO: