Support nullable arguments and default values for DI container configuration #181
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 optional values in container configuration and support for nullable arguments and default values in factory functions:
The previous version would always omit parameters with default values and nullable values without checking if an explicit container variable is set. We now first check to see if an explicit container variable is set and use this value if available. If this value is not available, we continue using the default value or a
nullvalue. This is the next step in adding better configuration support and support for (optional) environment variables and.env(dotenv) files as discussed in #101.Builds on top of #180, #179, #178, #163, #97, #95 and others