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

[envprovider] - If env is set to empty string, fallback to default #11776

Closed
wants to merge 5 commits into from

Conversation

VihasMakwana
Copy link
Contributor

See #11531 (comment)

In my opinion, we should fallback to default when either:

  1. env variable is unset
  2. env variable is set, but is an empty string

@VihasMakwana VihasMakwana requested a review from a team as a code owner November 29, 2024 14:17
Copy link
Member

@dmitryax dmitryax left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It needs discussion before changing the behaviour. See #11531 (comment)

Copy link
Contributor

This PR was marked stale due to lack of activity. It will be closed in 14 days.

@github-actions github-actions bot added the Stale label Dec 17, 2024
@VihasMakwana
Copy link
Contributor Author

After some thought over Dmitry's comment,

There must be a way to pass an empty string even if there is a default.

I agree. I'll close this issue. I think it's better to consider the empty string because the user might have explicitly set it to "".

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

Successfully merging this pull request may close these issues.

2 participants