Rename wagtail-specific app and remove django-flags duplication #29
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.
This PR corresponds to cfpb/django-flags#1 and closes #28.
This is the wagtail-flags side of splitting this library up into a pure-Django flags library and one that provides Wagtail support on top of that.
This is a breaking change, sort of. This PR does two major things:
wagtailflags
. Django-Flags will adopt theflags
app.Any Django projects that were previously using
wagtail-flags
will now need to make sure they include the following apps inINSTALLED_APPS
:Because Wagtail-Flags requires Django-Flags, only including
flags
will mean that all previous functionality continues as expected (except for WagtailSite
-based flag conditions), but the Wagtail admin UI will be gone.That is why this will be version 3.0.0.
This PR won't pass CI until cfpb/django-flags#1 is merged.