Add support for loading recursive environment variables from Container
#288
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.
This changeset adds support for loading recursive environment variables from the
Container. With these changes applied, factory functions may now explicitly reference their own variable name, which is especially useful for applying default values or casting or jugglingstringenvironment variables to their expected type likeintorfloat:This includes a number of updated tests to verify correct behavior and avoid introducing any potential regressions, so this has 100% code coverage and should be safe to apply. On top of this, I've updated the documentation slightly to showcase how this could be used to apply a default for the
X_LISTENenvironment variable. This is the next step in adding better configuration support and support for environment variables and.env(dotenv) files as discussed in #101.Builds on top of #287, #286, #284, #184, #38, and others