route-handlers-execution-rules

command
v12.2.0 Latest Latest
Warning

This package is not in the latest version of its module.

Go to latest
Published: Mar 11, 2023 License: BSD-3-Clause Imports: 1 Imported by: 0

Documentation

Overview

Package main is a simple example of the behavior change of the execution flow of the handlers, normally we need the `ctx.Next()` to call the next handler in a route's handler chain, but with the `ExecutionRules` we can change this default behavior. Please read below before continue.

The `Party#SetExecutionRules` alters the execution flow of the route handlers.

For example, if for some reason the desired result is the (done or all) handlers to be executed no matter what, even if no `ctx.Next()` is called in the previous handlers:

app.SetExecutionRules(iris.ExecutionRules {
  Begin: iris.ExecutionOptions{Force: true}, # begin handlers(.Use)
  Main:  iris.ExecutionOptions{Force: true}, # main handler (.Handle/Get...)
  Done:  iris.ExecutionOptions{Force: true}, # done handlers (.Done)
})

Note that if `true` then the only remained way to "break" the handler chain is by calling the `ctx.StopExecution()` (now that `ctx.Next()` doesn't even matter).

These rules are per-party, so if a `Party` creates a child one then the same rules will be applied to that as well.

Reset of these rules to their defaults (before `Party#Handle`) can be done with `Party#SetExecutionRules(iris.ExecutionRules{})`.

Jump to

Keyboard shortcuts

? : This menu
/ : Search site
f or F : Jump to
y or Y : Canonical URL