You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This should be a fairly straightforward command type.
It should be used to signal that a command will handle a route.
Which route the command will handle is determined by the [ValidatePattern] and [ValidateScript] attributes on the ScriptBlock (specifically, those that have an .ErrorMessage that starts with $Request)
Because the aspects related to command types should respect order, one could effectively route through several possibilities at fairly low cost (we'd checking the validations for every script, and only running what fits)
As with Parsers (#553), Routes should support multiple potential suffixes. That is:
Route,Routes,Router should all be considered Routes.
This command type should be extended for ease of integration:
This should be a fairly straightforward command type.
It should be used to signal that a command will handle a route.
Which route the command will handle is determined by the
[ValidatePattern]
and[ValidateScript]
attributes on the ScriptBlock (specifically, those that have an .ErrorMessage that starts with$Request
)Because the aspects related to command types should respect order, one could effectively route through several possibilities at fairly low cost (we'd checking the validations for every script, and only running what fits)
As with Parsers (#553), Routes should support multiple potential suffixes. That is:
Route
,Routes
,Router
should all be considered Routes.This command type should be extended for ease of integration:
Route.Command.Validate
should determine if a Route is Valid #695PipeScript should also include a few "default" routes:
The text was updated successfully, but these errors were encountered: