Skip to content
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

Deletion of code lists in the content library #13950

Closed
TomasEng opened this issue Oct 30, 2024 · 2 comments · Fixed by #14419
Closed

Deletion of code lists in the content library #13950

TomasEng opened this issue Oct 30, 2024 · 2 comments · Fixed by #14419

Comments

@TomasEng
Copy link
Contributor

TomasEng commented Oct 30, 2024

It should be possible to delete unused code lists from the content library.

Acceptance criteria

  • It is possible to delete an unused code list from the content library
  • It is not possible to delete a code list that is in use
  • The content library provides information telling the user that certain code lists cannot be deleted because they are in use

Out of scope

  • Handling deletion of code lists in use (deleting the components that use the code list etc.)

Decision points

We need to decide how to communicate to the user that a code list cannot be deleted because it is in use. Options to consider:

  • Display an alert when the user attempts to delete a code list in use
  • Add some visual details making it clear that the code list is in use (e.g. list the components that refer to it) and disable the delete button

Dependencies

@wrt95
Copy link
Contributor

wrt95 commented Nov 13, 2024

We have agreed to go for the first point:
Display an alert when the user attempts to delete a code list in use

@standeren
Copy link
Contributor

As a part of this issue we also need to implement support for checking where (in ComponentID or LayoutName or both?) the code list is used in the layouts.

@standeren standeren moved this from ⚠️ Blocked to 📈 Todo in Team Studio Dec 12, 2024
@standeren standeren moved this from 📈 Todo to 👷 In Progress in Team Studio Jan 14, 2025
@standeren standeren self-assigned this Jan 14, 2025
@standeren standeren linked a pull request Jan 14, 2025 that will close this issue
3 tasks
@github-project-automation github-project-automation bot moved this from 👷 In Progress to Documentation in Team Studio Jan 16, 2025
@standeren standeren moved this from Documentation to ✅ Done in Team Studio Jan 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: ✅ Done
Development

Successfully merging a pull request may close this issue.

3 participants