Do we need HighlightRange?

[gked]

Moving the original issue from https://github.com/dlibby-/highlight/issues/15

@Reinmar as FYI

To avoid defining a new subclass of Range, perhaps the entire API could be somehow built around the HighlightsMap.

const range = new Range();

const highlight = document.highlights.create( 'example-highlight', range, {
    priority: 1
} );

highlight.style.color = 'red';
highlight.priority = 42;

document.highlights.remove( range );

HighlightsMap#create() doing create&add at once is not the prettiest method, but maybe something along these lines could work. Having those new properties (style, priority, label) in some new interface (rather than squashed together with Range's properties) might avoid creating one giant class.

[sanketj]

@Reinmar Thanks for your feedback about HighlightRange being redundant. We have evolved the proposal since it was initially published and we no longer use this concept. Instead, we introduced a HighlightRangeGroup type, which holds a set of ranges that can be styled together, and that’s what gets added to the highlight map. Let us know if you have any additional comments about this. I will provide responses to your other issues separately.

[sanketj]

Closing this issue as it seems to have been addressed. Please feel free to reactivate if you have any additional concerns.