Support optional dependencies and unify @Dependency property wrappers #91
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.
Support optional dependencies and unify @dependency property wrappers
♻️ Current situation & Problem
As of right now, we support infrastructure for two property wrappers
@Dependency
and@DynamicDependencies
. The latter one induces particularly hard to understand syntax.This PR revises the dependency infrastructure and removes
@DynamicDependencies
by introducing a result-builder-based approach.Below code example demonstrates the difference:
⚙️ Release Notes
@DynamicDependencies
in favor of a new DSL-based approach used within the@Dependency
property wrapper directly.📚 Documentation
Documentation was updated.
✅ Testing
Functionality was verified with existing test cases. New tests were added for new functionality.
📝 Code of Conduct & Contributing Guidelines
By submitting creating this pull request, you agree to follow our Code of Conduct and Contributing Guidelines: