feature: post filtering on subscriptions #478
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Can you please update the docs as well with this? |
|
Docs updated |
|
@StorytellerCZ Any ideas what happened with 2.3.1 tests? I tried with the same version locally, it's running fine. |
|
Looks like an issue in the test setup... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What are we trying to solve with this PR?
For each named query, you should specify a body server-side in
createNamedQueryfunction and these are the fields that can be fetched. Additional fields requested from the client will be ignored.Additionally, you can also use
embodyto further limit the fields sent to a particular user.But what if you want to send limited fields for users depending on a value inside a document? This PR focuses on that with
subscriptionFilteroption where you can access the document in a subscription and change it (remove fields or similar) on the fly before it is sent to the client(s).Works with scoped queries.
Please see tests for better understanding.