fix: handle alias file with no orgs
prop
#969
Merged
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.
What does this PR do?
makes the alias accessor handle alias files that don't have the
orgs property (we got 2 reports happening where they get a alias file with
{}` as the content, should also fix users on the old key:value alias file format).repro:
write
{}
to your alias file (~/.sfdx/alias.json)run
SF_ENV=development sf alias list
, see errorthen if you link this branch of core into plugin-settings, with the same alias file you shouldn't get the error.
expected
sfdx-core handles bad alias file, returns "no alias found"
actual result
What issues does this PR fix or reference?
@W-14365013@