Reduce the Usage of Manual Type Erasure #12
Merged
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.
Reduce the Usage of Manual Type Erasure
♻️ Current situation & Problem
The current version of the framework uses different type erasure types that enabled a faster prototyping designing the external APIs at the beginning of the project.
💡 Proposed solution
This PR uses the Swift 5.7
any
andsome
keywords to reduce the reliance on type erasures in the project. It also ensures that components defined in a configuration are passed in a type-safe through the Dependency Manager in a type-safe way.Code of Conduct & Contributing Guidelines
By submitting creating this pull request, you agree to follow our Code of Conduct and Contributing Guidelines: