Evaluating Effect.Tag and Effect.serviceFunctions: Convenience or Anti-Pattern?
Are Effect.Tag and Effect.serviceFunctions etc anti patterns? I quite strictly put all of my code in services (and get all of my dependencies at the top of the constructor), but still find it tedious to have to put all of my implementation within the scope of the constructor. So those functions seem tempting but they also look like an anti pattern because they violate the rule of getting all dependencies in the service constructor.
