Models and Schemas, Batch 3: Task Management #140
Merged
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 is the third batch of models and schemas for #72, making up something like a simple task management system.
Changes
Models, schemas, and doc/docstring updates for:
Tier
Department
User
Story
(Replacement forProject
in this model set to reduce confusion with theProject
that's part of the models defined in tests.)Task
One thing I want to note is that, in
docs/advanced/joins.md
, the examples between the "Getting Joined Data Nested" section and the later "One-to-One Relationships" appear to be identical? It feels unnecessarily redundant to me, but I'm not sure what to do about it. I just wanted to get it noted for the review and see if anyone else who reads this has any ideas.Checklist