Add <g> tags to several components to aid with testing and DOM organization#30
Merged
Merged
Conversation
aeturnumfluctus
approved these changes
Jun 5, 2026
aeturnumfluctus
left a comment
aeturnumfluctus
left a comment
Collaborator
There was a problem hiding this comment.
looks good to me
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR helps aid the caller in organizing and testing their data within the Plox graphs by adding
<g>tags around several of our components. This tag allows us to tie a DOM id to groups of SVG elements that make up our data visualization, which can help aid in testing the actual contents of the graph which was previously difficult to do.Screenshot: