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

Retain layout changes after page reloads in UI #3120

Closed
ashrafgt opened this issue May 28, 2020 · 4 comments · Fixed by #3126
Closed

Retain layout changes after page reloads in UI #3120

ashrafgt opened this issue May 28, 2020 · 4 comments · Fixed by #3126
Assignees
Labels
type/feature Feature request

Comments

@ashrafgt
Copy link

ashrafgt commented May 28, 2020

Summary

Argo UI currently provides a few neat ways to modify the visual layout of the workflow(s) and filter steps/tasks. But changes are not retained following a page reload.

Motivation

Especially for very large and complex workflows, UI customization actions become quite repetitive.

Proposal

A simple save/load process using local storage may be sufficient.


Message from the maintainers:

If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.

@ashrafgt ashrafgt added the type/feature Feature request label May 28, 2020
@simster7 simster7 self-assigned this May 28, 2020
@simster7
Copy link
Member

I figured this would come up at some point. I'll take a look at this

@alexec alexec added the ui label May 28, 2020
@alexec
Copy link
Contributor

alexec commented May 28, 2020

This sounds specifically like the DAG display.

This needs some polish. It'd be good to fix with #3092 and #3091.

@ashrafgt
Copy link
Author

Thank you.

@alexec
Copy link
Contributor

alexec commented May 28, 2020

This needs some polish. It'd be good to fix with #3092 and #3091.

I'll fix #3091.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/feature Feature request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants