docs: clarify per-handler event transformer semantics (#3248)#4819
Open
champ96k wants to merge 1 commit into
Open
docs: clarify per-handler event transformer semantics (#3248)#4819champ96k wants to merge 1 commit into
champ96k wants to merge 1 commit into
Conversation
Each registered event handler operates on its own independent stream pipeline. Different handlers with different transformers do not affect each other's execution. - Add 'Per-Handler Event Transformers' section to bloc-concepts.mdx - Clarify doc comments in all bloc_concurrency transformers - Clarify that 'no event handler overlap' refers to the specific handler using the transformer, not other handlers on the same Bloc Part of felangel#3248
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.
Status
READY
Breaking Changes
NO
Description
Each registered event handler operates on its own independent stream pipeline. Different handlers with different transformers do not affect each other's execution.
Changes
Per-Handler Event Transformerssection tobloc-concepts.mdxexplaining eachon<E>()call creates an independent subscription that filters the shared event stream by type and applies its own transformer, with a Dart example showing two handlers with different transformers on the same Bloc.bloc_concurrencytransformers (sequential,restartable,droppable,concurrent) that their guarantees apply per-handler, not across handlers.Related Issues
Part of #3248
Type of Change