chore(fixtures): add Java and Kotlin fixtures for Android app entrypoints #245
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
hassankhan
force-pushed
the
twodoorsdev/add-android-fixtures
branch
from
8916bc8
to
b6b6327
Compare
Co-Authored-By: Bill Spooner <[email protected]>
hassankhan
force-pushed
the
twodoorsdev/add-android-fixtures
branch
from
b6b6327
to
c6a066e
Compare
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.
Why
The extra fixtures are useful when testing config plugins that make modifications to those files.
How
The Java entrypoints were a little harder to get a hold of, but were eventually retrieved from a project on RN v0.64. The Kotlin entrypoints were retrieved from a fresh Expo prebuild output.
Test Plan
None, as this is testing code.