Clarify env() behavior after config caching #10513
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Clarify env() behavior after configuration caching The current documentation states that “all calls to the env function will return null” once the configuration has been cached. However, this is only true for environment variables defined exclusively in the .env file. If the environment variable exists at the system level (e.g., via putenv(), server configuration, env() will still return a value after caching. This clarification helps developers understand that env() is not completely disabled after config:cache, but rather depends on the source of the environment variable.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Clarify env() behavior after configuration caching The current documentation states that “all calls to the env function will return null” once the configuration has been cached.
However, this is only true for environment variables defined exclusively in the .env file.
If the environment variable exists at the system level (e.g., via putenv(), server configuration, env() will still return a value after caching.
This clarification helps developers understand that env() is not completely disabled after config:cache, but rather depends on the source of the environment variable.