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

fix(3253): allow time range picker to render based on correct input selection #1301

Closed
wants to merge 14 commits into from

Conversation

VonnyJap
Copy link
Member

Context

Currently, when users select a time range in the job template view, the dropdown always defaults to "1 yr" instead of retaining the selected time range. This behavior results in a poor user experience, as the time range is not properly applied or displayed according to user input.

Objective

The goal of this PR is to fix the time range selection behavior in the job template view. The time range dropdown should accurately display and apply the user's selected value, ensuring that the selection is preserved and reflected correctly in the UI.

References

screwdriver-cd/screwdriver#3253

License

I confirm that this contribution is made under the terms of the license found in the root directory of this repository's source tree and that I have the authority necessary to make this contribution on behalf of its copyright owner.

Comment on lines 36 to 37
// 'none' option should not be available as options
this.timeRanges = this.timeRanges.filter(range => range.alias !== 'none');
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This doesn't do anything. When the class is created, timeRanges will not have anything to filter as none does not exist in the initial array in L10-20

@VonnyJap
Copy link
Member Author

I encountered issues with the commit history, so I’m closing this PR to address them.

@VonnyJap VonnyJap closed this Dec 16, 2024
@minghay minghay deleted the template-timepicker-fix branch February 4, 2025 20:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants