Fix issue with additional migrations being generated upon change of coupon types setting #24
+2
−2
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
…oupon types setting
blablacio
changed the title
digicase
added a commit
to digicase/django-coupons
that referenced
this pull request
Mar 11, 2020
Fix issue with additional migrations being generated upon change of coupon types setting byteweaver#24
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.
When generating migrations after changing the coupon types from settings, Django picks it up and creates a new migration in coupons app.
This is an unwanted side effect that should be avoided and easiest work around for now is to directly point migrations to settings.