Use AuthedRelationship to power byTracking #2811
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.
NOTE: The failing test is due to a different bug fixed in #2813
Noticed some of this logic was duplicated, so figured we could just re-use what exists to simplify the byTracking code.
Things
AuthedRelationship
handles for us:{ create: false, read: true, update: false }
createdBy
value on creationThings
AuthedRelationship
fixes for us:access: { ... }
syntax. ie; to toggleread: false
, all it takes is aaccess: { read: false }
instead of currently which requires re-specifying all three options, potentially leading to subtle bugs which make the access too permissive.isRequired
flag on create