Skip to content

Conversation

@btea
Copy link
Contributor

@btea btea commented Dec 16, 2025

If the value of envPrefix contains only spaces, it should probably be treated as an empty string.

@btea
Copy link
Contributor Author

btea commented Dec 16, 2025

Based on the test cases, it seems that strings containing only spaces are allowed.

However, simple spaces seem meaningless; do we need to handle them specially? 🤔

@bluwy
Copy link
Member

bluwy commented Dec 17, 2025

I think we can remove that edge case in the tests. It doesn't make much sense since you can't use spaces in env vars the command line, or in an .env file. The only way is to set in process.env[" spaces "] manually but this also feels very rare to support for me.

@btea btea changed the title fix: treating pure spaces as empty string fix: envPrefix should not contain spaces. Dec 17, 2025
@btea btea changed the title fix: envPrefix should not contain spaces. fix: envPrefix should not contain spaces Dec 17, 2025
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

Successfully merging this pull request may close these issues.

2 participants