Fix SVG id collisions by using random UUIDs instead of element IDs #368
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Checklist
I added multiple screenshots/screencasts of my UI changesI translated all the newly inserted strings into German and EnglishMotivation and Context
In ls1intum/Artemis#8823 some markers are missing from the solution diagram.
References for this issue:
https://stackoverflow.com/questions/37000385/multiple-svg-with-same-ids
https://stackoverflow.com/questions/54349169/svg-marker-disappears-when-svg-with-identical-definition-is-hidden
Description
To prevent such id collisions on the same page in the future, I changed it to use a random UUID instead of the
element.id
.Steps for Testing
Check if the
<marker>
elements have now a random uuid, by exporting multiple times.Test Coverage
no change
Screenshots
no change