Closed matusdrobuliak66 closed 2 weeks ago
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 88.60%. Comparing base (
d3e12a3
) to head (ef71774
).
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code
@odeimaiz I was thinking it might be useful to show a pop-up when a user is deleting a tag, indicating that the tag will also be removed from the Resource Usage history
What do these changes do?
Goal/Current Use Case:
Current Challenges:
project_tags
table poses an issue: if a project is deleted, its information would be lost and would no longer be listed. (Currently, the RUT maintains the complete history of runs, so it needs access to the project tags even after the project are deleted.)Proposed Solutions:
Primary Solution:
Use the
project_tags
table, but instead of deleting rows when a project is deleted, mark them as deleted. This ensures they are not listed anymore but remain accessible for historical purposes.Alternative Solution:
Keep a second copy of the
project_tags
table in the RUT. However, this introduces challenges in maintaining synchronization—not only when a tag is added or removed from a project, but also when the tag resource itself is deleted or updated. (started to implement but I do not think it is a good way to go:https://github.com/ITISFoundation/osparc-simcore/pull/6708)I found solution 1. more reasonable to implement.
Implemented behavior:
Related issue/s
How to test
Dev-ops checklist