It's totally fine and the preferred way to use services, of course, nonetheless, using context can reduce an necessary code when you just want to pass input to descendant components.
How does it reduce code? I don't see that argument. because a simple service that uses only public properties and be provided and injected isn't more code than this approach AND it stays in the pattern suggested by the framework.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Why not use scoped Services as intended by the framework. This approach seems overly complicated
It's totally fine and the preferred way to use services, of course, nonetheless, using context can reduce an necessary code when you just want to pass input to descendant components.
How does it reduce code? I don't see that argument. because a simple service that uses only public properties and be provided and injected isn't more code than this approach AND it stays in the pattern suggested by the framework.