NSRange to Range<AttributedString.Index> conversion should be relative to sliced boundaries #1050
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.
When converting an
NSRange
to aRange<AttributedString.Index>
via our API, the conversion currently does not take the providedAttributedStringProtocol
'sstartIndex
/endIndex
into account. This means that theNSRange
's location is considered relative to the base's start for anAttributedSubstring
rather than the substring's start, leading to conversion failing because theNSRange
is often considered beyond the bounds of the slice.This updates the conversion to operate on a slice of the underlying
BigString
so that the range calculation is performed from the slice'sstartIndex
rather than the base'sstartIndex
.