Update view responses to return modified data #353
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.
The Django views are currently inconsistent in what they return for
PUT
orPOST
requests. It's hard to say what the general convention or consensus seems to be regarding this point, but in our specific use case, it's easier to handle responses in the frontend queries if all endpoints return the modified or created resource. This way, we don't need to pass down any other fields from parent components (we'd only need the immediately relevant fields for the request, not the effects of the request), and the query handler has all the information necessary to invalidate any queries.In the process of making this change, the views files have also been reformatted.