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

toolbar: add n-window-selector #1755

Merged
merged 3 commits into from
Apr 24, 2024
Merged

Conversation

oliver-sanders
Copy link
Member

@oliver-sanders oliver-sanders commented Apr 16, 2024

  • Closes configurable n-window #864
  • Add a selector for switching the n-window extent between 0 & 3 inclusive.
  • The n-window value appears to be preserved when navigating back to the workflow.

n-window-changing

Check List

  • I have read CONTRIBUTING.md and added my name as a Code Contributor.
  • Contains logically grouped changes (else tidy your branch by rebase).
  • Does not contain off-topic changes (use other PRs for other changes).
  • Applied any dependency changes to both setup.cfg (and conda-environment.yml if present).
  • Tests are included - seems to be hard to test meaningfully without true e2e tests (i.e. with live workflows).
  • CHANGES.md entry included if this is a change that can affect users
  • docs issue - changes: document cylc-ui#1755 cylc-doc#719
  • If this is a bug fix, PR should be raised against the relevant ?.?.x branch.

@oliver-sanders oliver-sanders added this to the 2.5.0 milestone Apr 16, 2024
@oliver-sanders oliver-sanders self-assigned this Apr 16, 2024
@oliver-sanders
Copy link
Member Author

oliver-sanders commented Apr 16, 2024

@MetRonnie, this setting is preserved when you navigate back, however, I have not done anything to achieve this. Should it be implemented differently or is this ok? (note the n=1 default comes from cylc-flow not cylc-ui)

@MetRonnie
Copy link
Member

It's preserved because it's querying it, right?

@oliver-sanders
Copy link
Member Author

oliver-sanders commented Apr 16, 2024

Derp, yes, it's getting the n-window extent from the returned data 🤦

@oliver-sanders
Copy link
Member Author

As a true end-to-end feature (i.e. flow-uis-ui-uis-flow) it's a right pain to test. I had a look a testing, at the unit test level you end up testing vue watchers and at the e2e level, you end up testing the Vuetify Select API.

* Closes cylc#864
* Add a selector for switching the n-window extent between 0 & 3
  inclusive.
* The n-window value appears to be preserved when navigating back to the
  workflow.
Co-authored-by: Ronnie Dutta <61982285+MetRonnie@users.noreply.github.com>
Copy link
Member

@hjoliver hjoliver left a comment

Choose a reason for hiding this comment

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

Tested, love it.

@oliver-sanders oliver-sanders merged commit 9b75091 into cylc:master Apr 24, 2024
7 of 8 checks passed
@oliver-sanders oliver-sanders deleted the n-window branch April 24, 2024 08:07
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.

configurable n-window
3 participants