RFC: Interceptor middleware chain#23
Open
joshuajbouw wants to merge 1 commit into
Open
Conversation
Priority-ordered event dispatch with Continue/Final/Deny short-circuit semantics. Separated from capsule interface system RFC — different concern (dispatch architecture vs interface contracts).
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.
Priority-ordered event dispatch with short-circuit semantics. Interceptors return Continue, Final, or Deny to control the middleware chain.
Split from the capsule interface system RFC (#20) — the interceptor chain is a dispatch architecture concern, not an interface contract concern. Different audiences: this RFC is for capsule authors building guards, caches, and transforms.