-
Notifications
You must be signed in to change notification settings - Fork 477
[expo-cli] consolidate env variables. #2358
Conversation
Tests are failing but unrelated to our PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks for taking care of this one 🙏
Since we were prioritizing the environment variable over the flag before, and now we're doing the opposite, this still might constitute a breaking change (although I do agree that if both are provided, it seems intuitive to fallback to whatever was provided by the flag).
We could keep the original behavior, but if you provide both and they aren't equal, we log an error? something like
You've provided contradictory Apple IDs. You should provide either [env var] or [flag], not both. Falling back to [whichever we fall back to].
unrelated- we'll need to update the docs as well
Thanks for catching the missing docs, updated! Regarding the breaking behavior, we had discussed this and think that this is the intuitive behavior and further this happens only when a user is doing multiple things wrong so we felt comfortable moving ahead with it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just one typo fix
this happens only when a user is doing multiple things wrong
I wouldn't say passing both the flag and the env variable is necessarily wrong, but if we are changing this then might as well add a changelog entry listing this as a bug fix so it's easily identifiable for that extremely rare case where someone maybe was relying on this behavior
Co-authored-by: Charlie Cruzan <35579283+cruzach@users.noreply.github.com>
|
This fixes #2280.
NB: in case of conflict we chose to prioritize the flag over the env variable.
Joint with @quinlanj
tests
expo upload:ios
with flags and env var