Add fragmentIdentifier for anchor links #97
Merged
Conversation
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
adgad
reviewed
Sep 5, 2025
Collaborator
adgad
left a comment
adgad
left a comment
There was a problem hiding this comment.
Looks good to me!
Currently in Spark / bodyXML, I believe we only support adding fragment identifier on Heading, ImageSet, Flourish are all the other nodes expected to be supported soon? If it's going to be a while, should we split up the PR to only do the ones that will work today?
Contributor
Author
@adgad Thanks for spotting. I've created a new PR for just |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.