openedx / openedx/frontend-app-authoring
Standardize deletion and removal confirmations
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 17
- Forks
- 218
- Avg merge
- 9d 20h
- Merged PRs (30d)
- 20
Description
When deleting a library object, we want to make sure users understand that it will be:
- Removed from other library objects it was previously part of, if any (https://github.com/openedx/frontend-app-authoring/issues/1685)
- Unlinked from local objects used in courses
Spec
- When a library object that has already been used in a course is deleted in a library, the warning that course objects will be unlinked should be included
- The warning can link to the specific course, or list multiple courses
- When a library object not used in a course is deleted, the warning should be omitted.
Rough mockup (copy to be adjusted)
UX/UI tasks
- Generate spec/mockups of confirmation dialog conditional on: course reuse, library reuse, library object level
- Edit copy
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the deletion confirmation flow and the linked frontend-app-authoring issue 1685. Define the dialog states for course reuse, library reuse, and library-object level, then update the copy and verify that course-unlink warnings appear only when applicable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100