-
Notifications
You must be signed in to change notification settings - Fork 29
Users should be able to delete their own submissions #175
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
Comments
|
@Oanh-and-only-Oanh please help with these questions |
|
@Oanh-and-only-Oanh @sushilshinde Should this be carried out immediately or should I hold until soft delete feature is implemented (Currently, there's no plan for soft delete yet but I am guessing it is in the pipeline) |
@callmekatootie, what's the LOE and how long will it take to carry out now? |
@Oanh-and-only-Oanh Should wrap up in 1-2 days |
@Oanh-and-only-Oanh Just making sure - I am waiting on the go ahead from you here. I want to know if I can proceed or if I need to wait for Soft Delete. Also - the 1-2 days timeline is for the feature request in this ticket - NOT for soft delete. |
apologies for the late reply @callmekatootie. For some reason I don't get notified of mentions in github. Yes, please more forward with feature request. thank you. |
Status: PR ready. Reviewer assigned to review |
@Oanh-and-only-Oanh the changes are in develop branch / dev instance of topcoder. If we need to move the changes to production, kindly let me know |
@callmekatootie hold on this. |
Problem described in the topcoder-platform/community-app#4213
Cause: V5 submission API delete endpoint only allows admin roles to delete the submissions.
Effect: Community app is using V3 delete endpoint instead of v5, which is probably wrong as back DB is architecture is different for V5, and submissions doesn't reflect the delete action.
Requirement: Users should be able to delete their own submissions
@Oanh-and-only-Oanh @callmekatootie
The text was updated successfully, but these errors were encountered: