Add reactive event handler runtime - #10
Merged
Merged
Conversation
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
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.
Summary
reactivemodule with provider-neutral event inputs, pure handlers/hooks, route matching, canonical ordering, dedupe, reports, and cache effect applicationEventDecoderHandleradapterValidation
cargo test --test reactive_runtimecargo test --test event_pipelinecargo test --test public_release_surfacecargo testcargo test --no-default-featurescargo fmt --all --checkcargo clippy --all-targets --no-deps -- -D warningsRUSTDOCFLAGS="-D warnings" cargo doc --no-depsRUSTDOCFLAGS="-D warnings" cargo doc --no-deps --no-default-featurescargo +1.88.0 check --lib --lockedgit diff --checkNotes
AlloySubscriberis intentionally a scaffold and returnsUnsupported; live transport wiring, executing resync scheduling, and full reorg journaling remain follow-up work.