Adding missing migration. #12
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
Fixed django warning
… dictionary did not contain the `messageDetails` key. So instead we add the entire message dictionary to the job for more useful debugging information.
|
Going to move this change into its own branch and reopen new merge request for just this change. |
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 running make migrations for my project I noticed that an additional migration was being created for this app. The only difference that I saw between this migration and the initial migration is that the initial migration uses byte strings for the choices.
Looking at the history for the models file it doesn't look like the state choices were ever byte strings. It looks like they were added to the migration when the migrations were changed to be compatible with Django 1.8.