This repository has been archived by the owner on Jan 18, 2024. It is now read-only.
[xdl] clean up Expo.plist artifacts left behind by IosPlist util #2028
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.
The
IosPlist
util leaves behind some artifacts (*.json
,*.plist.bak
) which may be confusing to users who aren't expecting them.In particular, users running
expo publish
in a bare workflow project withexpo-updates
may find these extra files (which come from modifying the data in the Expo.plist config file) confusing. Their utility is limited -- since most people are using version control there's no need to have separate backup files in the same folder. So in this case we should just delete those files after theIosPlist.modifyAsync
operation completes successfully.Test plan
expo init
, bare-minimum template,expo publish
expo publish
producesExpo.json
andExpo.plist.bak
files in the Supporting direxpo publish
no longer produces those filesfs.removeSync
is a no-op