Improve spannable support performance #44
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
Spanable support is now enabled by default. The documentation and readme have been updated accordingly. An affected unit test has been updated. When NativeCore#setSupportSpannable(true) was called, strings were processed by fromHTML() even when they contained no tags. Since fromHTML() has a performance cost, we had a perfomrance penalty even when we didn't need it. With this update, we apply fromHTML() only in strings that contain a "<" character and hence probably contain tags. This way, the performance penalty occurs only when needed.
n1k0sv
approved these changes
Sep 29, 2022
Merged
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.
Spanable support is now enabled by default. The documentation and readme have been updated accordingly. An affected unit test has been updated.
When NativeCore#setSupportSpannable(true) was called, strings were processed by fromHTML() even when they contained no tags. Since fromHTML() has a performance cost, we had a perfomrance penalty even when we didn't need it.
With this update, we apply fromHTML() only in strings that contain a "<" character and hence probably contain tags. This way, the performance penalty occurs only when needed.