-
Notifications
You must be signed in to change notification settings - Fork 18
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
348 add deep linking to controls #544
Conversation
vanessuniq
commented
Mar 2, 2023
- Each control is wrapped in a hyperlink element that opens in a new tab. We can also select a control without clicking on the link.
- Alternatively, we can add a link icon to each control and wrap it in a hyperlink element.
Signed-off-by: Vanessa Fotso <vfotso@mitre.org>
Refactored Rules component to set the queried rule as the the selected rule and pass selected/open rules data top -> down (form parent to children) Added link to individual control, to be open in a new tab if clicked Used window.history method to change url in the browser without refreshing the page when selecting a control Signed-off-by: Vanessa Fotso <vfotso@mitre.org>
Signed-off-by: Vanessa Fotso <vfotso@mitre.org>
…as well, for user with no edit privilege Signed-off-by: Vanessa Fotso <vfotso@mitre.org>
992bcd4
to
868b225
Compare
Initial testing looks good. One minor "bug" is in the URL, if you change the component ID, but leave the rest, it will navigate you to the control in the new component with the same last 6 digits (looks like the "prefix" isn't being checked). |
More issues found... for example, unlocking a control doesn't refresh the screen. Then when changing the status, the other mandatory fields don't change like they're supposed to. Also, if typing into a field, then nagivating to another control, the text in the field doesn't change as expected. |
Hi @vanessuniq , I love the way I can get to any control by performing a GET. If I click, 4 or 5 controls on the page, its even getting delayed in loading the page & hitting the performance. Can we do something to cache the responses ? And did you observe this pattern at your end ? |
nice catch |
Yes, I noticed that. I did not want to change the workflow that was already in place, just build on top of it. This is due to several event listener within all involved Rules vue components that triggers axios. This workflow definitely needs to be optimized. |
Moving this to draft, continue working on the issues |
resolved with pr #546 |