Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Route Command Type #670

Closed
4 tasks done
Tracked by #554
StartAutomating opened this issue Nov 16, 2023 · 0 comments · Fixed by #866
Closed
4 tasks done
Tracked by #554

Route Command Type #670

StartAutomating opened this issue Nov 16, 2023 · 0 comments · Fixed by #866
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@StartAutomating
Copy link
Owner

StartAutomating commented Nov 16, 2023

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:

PipeScript should also include a few "default" routes:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Development

Successfully merging a pull request may close this issue.

1 participant