Skip to content
This repository has been archived by the owner on Jul 27, 2021. It is now read-only.

Remove Dispatch from Middleware Context #3

Closed
Andrei15193 opened this issue Apr 11, 2019 · 0 comments
Closed

Remove Dispatch from Middleware Context #3

Andrei15193 opened this issue Apr 11, 2019 · 0 comments
Assignees

Comments

@Andrei15193
Copy link
Owner

Currently (in beta1 and beta2) you can skip all the remaining pipeline elements by dispatching an action directly and not calling context.Next or context.NextAsync. This goes against the idea of a pipeline because the middleware handler can skip all following middleware (skip the pipeline).

The most control a middleware handler has over the action is whether it continues in the pipeline (acts as a filter) or continues in the pipeline either with the same action or a different one. A middleware handler may invoke to next handlers multiple times by calling context.Next or context.NextAsync multiple times (this can be the case of expanding actions that are in fact a Task to notify when the operation starts and when it completes).

@Andrei15193 Andrei15193 self-assigned this Apr 11, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant