Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Strange handling $ONE$TWO #103

Closed
oturpe opened this issue Oct 27, 2023 · 3 comments
Closed

Strange handling $ONE$TWO #103

oturpe opened this issue Oct 27, 2023 · 3 comments

Comments

@oturpe
Copy link

oturpe commented Oct 27, 2023

Consider the following env file:

NO_NO="NO_NO: $NO$NO"
YES_NO="YES_NO: $YES$NO"
YES_YES="YES_YES: $YES$YES"
NO_YES="NO_YES: $NO$YES"
YES_YESS="YES_YESS: $YES$YESS"

When NO is not defined and YES and YESS are defined, this results in:

NO_NO: 
YES_NO: yes
YES_YES: yesyes
NO_YES: 
YES_YESS:

In other words, if ONE and TWO are both defined, $ONE$TWO evaluates to undefined.
This is highly unintuitive.
I expect both variables to be expanded in this case.

As a workaround, ${ONE}${TWO} works as expected.

Version: 10.0.0

This used to work with 5.1.0.

@motdotla
Copy link
Owner

motdotla commented Feb 9, 2024

showing failing spec here: #108

@motdotla
Copy link
Owner

fixed here. will go out as part of v11.0.0 (should be released today or tomorrow) #108

@oturpe
Copy link
Author

oturpe commented Feb 10, 2024

Nice, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants