-
Notifications
You must be signed in to change notification settings - Fork 28
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
Conversation
@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) |
It's preserved because it's querying it, right? |
Derp, yes, it's getting the n-window extent from the returned data 🤦 |
a2b8e06
to
6eda79d
Compare
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.
f49f4cc
to
c5e13fb
Compare
Co-authored-by: Ronnie Dutta <61982285+MetRonnie@users.noreply.github.com>
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.
Tested, love it.
Check List
CONTRIBUTING.md
and added my name as a Code Contributor.setup.cfg
(andconda-environment.yml
if present).CHANGES.md
entry included if this is a change that can affect users?.?.x
branch.