feat: External query flows - add an alternative form of withQuery#21
Merged
Conversation
romychab
force-pushed
the
feat/external-query-flows
branch
from
July 5, 2026 11:06
1fa17c9 to
3b65547
Compare
…the Store builders that accepts a lambda returning a query `Flow` instead of an imperative query owned by the store.
romychab
force-pushed
the
feat/external-query-flows
branch
from
July 5, 2026 11:15
3b65547 to
f7a4f60
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
withQueryto the Store builders that accepts a lambda returning a queryFlowinstead of an imperative query owned by the store.container-storeskill - metadata patterns, newwithQueryusage, mention the common mistake with fabricating event bus or other observable patterns