Custom flag models #292
Closed
Custom flag models #292
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
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.
WAFFLE_FLAG_MODEL
The model that will be used to keep track of flags. Defaults to
waffle.Flagwhich allows user- and group-based flags. Can be swapped for a different Flag model that allows flagging based on other relationships or properties, such as an Organization a user belongs to. Analogous functionality to Django's extendable User models. Needs to be set at the start of a project.Obs.:Migrations do not support changing after the initial migration.This PR creates two abstract models to help users create their own Flag model with existing functionality:
AbstractBaseFlagandAbstractUserFlag.This is the same code written by @koliber here, I only rebased it.
fixes #181, fixes #286