fix: removeAt instead of removeLast for SDK <35 compatibility #226
Conversation
This file contains 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
This stack of pull requests is managed by Graphite. Learn more about stacking. |
This was referenced Jan 3, 2025
sargunv
changed the title
sargunv
changed the base branch from
android_disable_texture_mode
to
graphite-base/226
sargunv
force-pushed
the
fix_android_removeat_instead_of_removelast
branch
from
d1f848d to
b55d2e8
Compare
sargunv
force-pushed
the
graphite-base/226
branch
from
29f827a to
8e7c97e
Compare
sargunv
force-pushed
the
fix_android_removeat_instead_of_removelast
branch
from
b55d2e8 to
b9ec32c
Compare
Merge activity
|
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.
Run Android instrumentation tests against API levels 24 and 35, and fix a compatibility issue by using removeAt instead of removeLast.
fixes #224