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.
Using React Context to Dependencie Injection
Inside the Services folder we've got all set up for react context, provider and hook, there will be our entry point to inject new dependencies or replace.
An interesting point: If I needed to change a dependency to a specific use case? How would be? Since we're injecting the dependency to use for all useCase throughout our code base.
Anserw: Whenever you retrieve a context, the React's algoritm will reach to the CLOSEST provider available on the tree, that's it!
Need a specific dependencies for a use case? Just create another provider replacing the services for that specific use case!
P.S: this approach will replace the Implementations classes