Fix decorating error with dependencies bound with FastBind() #12
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.
FastBind()
had used a casting to implementation class during adding dependency to ViewModels container. This casting was used in the provider-method, that had being added to ViewModels container to get the dependency from main container. It had raised an error on attempt to decorate any dependency, that is bound this way, because decorator is not an inheritor of decorated class. So the decorator could not be casted to original implementation class.Now
FastBind()
do not use data about implementation this way and do not make any checks in ViewModels container provider-method.Decorating example was added to demo project to keep autotests catch errors in this functionality.