feat: track history of submission changes #1491
Open
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.
This is a "spike" into integrating
paper_trail
for lightweight tracking of submission changes (related to ONYX-1109). I followed the default setup instructions, and just overrode theuser_for_paper_trail
method for our 2 different use-cases (administrative requests, or API requests including via GraphQL). No user is tracked for logged-out updates, but that should be obvious from the submission data, I guess.I don't want to bloat the repo for no reason, but if this sort of history is useful, we could consider a few further updates, neither difficult: