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

Store the expanded state of the explorer trees locally #2143

Merged
merged 1 commit into from
Sep 11, 2017

Conversation

skateman
Copy link
Member

@skateman skateman commented Sep 8, 2017

As we're already storing the state on the server side and sending the tree already expanded when necessary, this doesn't do very much but it's a good start for the API-backed tree builders.

@martinpovolny @himdel

@miq-bot
Copy link
Member

miq-bot commented Sep 8, 2017

Checked commit skateman@f399f1b with ruby 2.2.6, rubocop 0.47.1, and haml-lint 0.20.0
0 files checked, 0 offenses detected
Everything looks fine. 👍

@himdel
Copy link
Contributor

himdel commented Sep 8, 2017

So.. what does it do? :)

@skateman
Copy link
Member Author

skateman commented Sep 8, 2017

Well, it stores the tree state in the sessionStorage as the previous implementation. It also expands/collapses the nodes if necessary but for now the ruby code does it for us. A piece of code we want to get rid of in the future 😉

@himdel
Copy link
Contributor

himdel commented Sep 11, 2017

And why key?

@skateman
Copy link
Member Author

@himdel because it's the unique identifier of each tree node. Again: we were using this before in the non-angular implementation. In the future I'd like to use a more complex key that consists two elements (type, id) and then we can drop the current key which is just too complex.

@himdel himdel merged commit 0029baa into ManageIQ:master Sep 11, 2017
@himdel himdel added this to the Sprint 69 Ending Sep 18, 2017 milestone Sep 11, 2017
@skateman skateman deleted the explorer-tree-persist branch September 11, 2017 20:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants