Add "type" field to Document model
#828
Open
Conversation
This file contains hidden or 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
1 participant
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.
Description
This PR adds a
"type"field to theDocumentmodel for the purpose of easily seperating Open5e source data ("type": "SOURCE") from auxilary assets that are used to support the operation of the Open5e website ("type": "MISC"). This setup will allow the two types of Documents to be easily seperated on the front-end by, for example, the Source Selector UI.Related Issue
Closes #756
How was this tested?
pytest(many test cases needed to be updated to reflect the changes to theDocumentmodel. Once this was accounted for all tests are passing)