-
Notifications
You must be signed in to change notification settings - Fork 266
Database Management #423
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
Merged
Merged
Database Management #423
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
922bde7 to
887ebe9
Compare
mistahj67
reviewed
Feb 28, 2024
elikmiller
requested changes
Feb 28, 2024
elikmiller
approved these changes
Mar 5, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This changeset adds a new page underneath "administration" that enables a user to obliterate their data.
3/1 UPDATE
the api contract has changed slightly to accommodate more flexibility in deleting asset group selectors. the request body used to have a boolean field named
deleteHighValueSelectors, which has been changed to the namedeleteAssetGroupSelectorsand it accepts a list of ints (corresponding to asset group id's)the ui has been updated with 5 checkboxes instead of 4:

api changes:
POST api/v2/clear-databaseui changes:
<DatabaseManagement />and<ConfirmationDialog/>componentsMotivation and Context
give a user the ability to light fire to their data
How Has This Been Tested?
unit tests have been added to cover UI changes, and unit and integration tests have been added for the api handler
Screenshots (if appropriate):
Types of changes
Checklist: