Pass the options object when fetching related data #2119
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.
Introduction
The
options
object is passed a bit everywhere and isn't passed to relations. By passing the options object into relations, this opens countless possibilities, such as filtering data according to logged-in user rights directly into the relation.Motivation
Our main use case is filtering related data according to the user rights. To be able to do this, we need to access a context object to know who is the logged-in user. Currently, relations can't be "dynamic" and adapt to a tenant or other contextual data.
Proposed solution
By simply passing the
options
object to the related fetching, we can implement something like this:Current PR Issues
I didn't encounter any issues up to now.
Alternatives considered
I've tried many ways to access some data from the relation function unsuccessfully.
Thank you for considering this PR.