Strictly type pipeline step parameters#530
Merged
PhilippMatthes merged 3 commits intomainfrom Feb 23, 2026
Merged
Conversation
PhilippMatthes
commented
Feb 19, 2026
Member
Author
|
Will rebase and polish this up. |
83d0689 to
3f6104b
Compare
SoWieMarkus
approved these changes
Feb 23, 2026
Contributor
Test Coverage ReportTest Coverage 📊: 68.7% |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Before we used runtime.Rawextension to load nested json into our scheduler steps, where the json is parsed into the schema expected by the scheduler step and then validated.
The goal of this change to spec this out more strictly. Instead of generic json substructs (runtime.Rawextension) the goal is to type the parameters strictly.