fix(eas-cli): avoid adding expo.extra
data from config plugins in eas init
#2554
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
This fixes the
eas init
command, where we currently merge theexpo.extra
data in the manifest with plugin-generated data. You can repro this through the steps defined in the test plan.How
expo.extra
object withexpo.extra.eas.projectId
Test Plan
$ bun create expo ./test-eas-init
$ cd ./test-eas-init
expo.extra
but does haveexpo.plugins[expo-router]
$ eas init
expo.extra
only containsexpo.extra.eas.projectId
, and nothing from the router plugin