Add option to specify a type for Highlighter serialization #291
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.
Optionally allow clients to specify a type for highlighter serialization different from the highlighter's type. In this way, clients can use the more responsive textContent type for creating highlights, but serialize the highlights into a TextRange format for better consistency across browsers.
Code play the same game done in deserialize that converts from one type to another when necessary.
If this doesn't fit with your roadmap, feel free to ignore, but I thought this might be of use to others. If there is a good reason why this is a bad idea, I'd love to hear it.