-
Notifications
You must be signed in to change notification settings - Fork 156
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
internal/relui, internal/workflow: add parameter type support
Previously, it was only possible to create workflow parameters with the implicit "string" type hard-coded. Some workflows we're creating either require or will benefit from more flexibility in parameter types (slices of strings, single-line vs multi-line strings, and so on). It was also not yet possible to associate metadata to parameters (such as documentation, example values). This change implements that flexibility for workflow parameters, and uses it to better document the existing Twitter workflows. The next change will add a workflow that uses new slice types. For simplicity and clarity reasons, all parameter information is contained in one place in the workflow.Parameter struct, including some fields that control the HTML presentation of said parameters, instead of trying to factor out HTML bits into the relui package and creating a bridge between the two. Also type check in more stages of the workflow processing. For golang/go#47405. Fixes golang/go#51191. Change-Id: Ia805b3b355e65fcbf2397ad21800da448ccb826a Reviewed-on: https://go-review.googlesource.com/c/build/+/404454 Reviewed-by: Dmitri Shuralyov <[email protected]> Run-TryBot: Dmitri Shuralyov <[email protected]> Auto-Submit: Dmitri Shuralyov <[email protected]> Reviewed-by: Heschi Kreinick <[email protected]> TryBot-Result: Gopher Robot <[email protected]>
- Loading branch information
Showing
10 changed files
with
292 additions
and
65 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.