-
Notifications
You must be signed in to change notification settings - Fork 11
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
Improve Catalog Control Group Navigation #602
Improve Catalog Control Group Navigation #602
Conversation
2a10b3b
to
191b370
Compare
191b370
to
5791be5
Compare
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.
I think we're pretty significantly missing a design for groups in groups in groups. And we're possibly changing the behavior of a control in a control.
The names of these components are also starting to imply that maybe we're losing a little insight into the spec. Remember that it's also possible to have controls without groups (in additions to just layers of groups all the way down).
I do not think we have ever tested that so I created https://raw.githubusercontent.com/EasyDynamics/oscal-demo-content/nested-groups/catalogs/NIST_SP-800-53_rev4_catalog.json. Things do get very broken. Although I also do not like how the |
2ecbf8f
to
daeb39c
Compare
9b2e2b5
to
e20afd6
Compare
e20afd6
to
5760511
Compare
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.
Really good progress here! Thanks! I think there are just a few more things I'd like to try to implement before merging this.
d113fb4
to
4676625
Compare
42dc407
to
7e279e9
Compare
@tuckerzp Do you think that you can provide a summary of the status of this PR? Is it ready for review again or are there additional things that need to be completed? |
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.
Thanks for your work on this! Just tested it locally and the new UI works great.
groupKey adds unneeded complexity to hash the title of groups as a key. group.title is required and unique according to the spec, so it can safely be used as a key.
I think functionality wise, everything is good to go. It is mostly stylistic issues brought up I need to address.
I know that the issue has this happening, but I am now not sure if that would be best. I just realized that after clicking on a tab and then using the up/down arrow keys, the currently selected box gets a really neat highlight feature. It is highlighted on the center of the tab, so I feel like having the text centered makes sense.
I got rid of
The issue I am having here is that sometimes the tabs are longer and sometimes the content is longer. Currently the line is a |
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.
While I don't think that this necessarily handles every edge case that we could throw at it, I do think it's a pretty nifty start. Thanks @tuckerzp. I am content with the design and the structure. You've put a lot of good effort into this and I appreciate it!
The specific issue highlighted has been addressed and "Request Changes" will block another review from approving/merging.
@tuckerzp This is really good work! I think the currently selected box highlighting feature is very cool. |
This uses
Tabs
from material ui to make a vertical menu to navigate catalog control groups. It also extracts sub groups to its own function.closes #88