[UI] Renamed 'Value' column to 'Iteration Value' in Outputs tab (#2066) #2070
Conversation
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
|
@H3m4N-14 your update are not is in the right place, I'm update the PR and merged THanks for the contributions |
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.
[UI] Renamed 'Value' column to 'Iteration Value' in Outputs tab (#2066)
This change renames the "Value" column to "Iteration Value" in the Outputs tab of the Kestra UI.
Issue #2066 requested this change to improve clarity, as the "Value" column is only used in tasks that iterate over values (such as "Each" tasks). By renaming the column to "Iteration Value," it becomes more apparent why this value is only available in those mapped tasks.
This commit aligns with the issue description and enhances the user experience when working with Kestra's UI.
close #2066