-
Notifications
You must be signed in to change notification settings - Fork 76
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
Delete and purge individual submissions #1150
Conversation
e6efdc2
to
c13b24c
Compare
e475cd2
to
6a7d9bf
Compare
df04c06
to
76e523b
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.
Interactive review
lib/model/migrations/20240914-02-remove-orphaned-client-audits.js
Outdated
Show resolved
Hide resolved
One thing I'm realizing is that for Frontend, we'll eventually need a way to list submissions in the trash, something like |
Completes the Backend portion of getodk/central#667
Adds submission delete endpoint that soft-deletes a single submission, and a mechanism to purge submissions deleted for more than 30 days.
Done:
submission.delete
verbStill to do (sept 9 2024)
What has been done to verify that this works as intended?
Why is this the best possible solution? Were any other approaches considered?
How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?
Does this change require updates to the API documentation? If so, please update docs/api.yaml as part of this PR.
Before submitting this PR, please make sure you have:
make test
and confirmed all checks still pass OR confirm CircleCI build passes