-
Notifications
You must be signed in to change notification settings - Fork 67
refactor: improve handling of workflow default values #3064
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
Merged
didier-wenzek
merged 6 commits into
thin-edge:main
from
didier-wenzek:refactor/workflow-default-values
Aug 21, 2024
Merged
refactor: improve handling of workflow default values #3064
didier-wenzek
merged 6 commits into
thin-edge:main
from
didier-wenzek:refactor/workflow-default-values
Aug 21, 2024
Conversation
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
Codecov ReportAttention: Patch coverage is Additional details and impacted files📢 Thoughts on this report? Let us know! |
Robot Results
|
albinsuresh
approved these changes
Aug 20, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Signed-off-by: Didier Wenzek <didier.wenzek@free.fr>
With the previous impl TryFrom<TomlExitHandlers> for Handlers many definition consistency and completness checks were not feasible, the default values being injected only once the struct fully built. This commit is a preparation step. The next step is to deprecate the `with_default` method, moving its effects into to the TryFrom implementations. Signed-off-by: Didier Wenzek <didier.wenzek@free.fr>
Signed-off-by: Didier Wenzek <didier.wenzek@free.fr>
The aim is to resolve all the workflow transitions when the workflow definition is parsed and not during its execution. Signed-off-by: Didier Wenzek <didier.wenzek@free.fr>
The idea is to force the users to be explicit on which state is to be used on a successful action. Using the terminal successful test being likely an error on most cases. Signed-off-by: Didier Wenzek <didier.wenzek@free.fr>
ac54e96
to
dfb916d
Compare
Signed-off-by: Didier Wenzek <didier.wenzek@free.fr>
albinsuresh
approved these changes
Aug 21, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
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.
Proposed changes
Inject workflow default values while parsing the workflow definition and not during execution.
When a workflow is used to execute an operation, all the transitions must have been resolved.
DefaultHandlers
of a workflowwith_default
methods from Handlerson_success
from theDefaultHandlers
.Types of changes
Paste Link to the issue
Checklist
cargo fmt
as mentioned in CODING_GUIDELINEScargo clippy
as mentioned in CODING_GUIDELINESFurther comments