I think it depends. I think services are most useful when communicating from a deeply nested child component directly to a high level parent component. I should have clarified that point because passing @Input properties down a deep chain isn’t as cumbersome as managing @Output properties back up the component chain.
So I guess to answer your question, it’s probably better to just pass @Input properties down to a dumb component but I wouldn’t say it’s an anti pattern to use a service
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.
I think it depends. I think services are most useful when communicating from a deeply nested child component directly to a high level parent component. I should have clarified that point because passing @Input properties down a deep chain isn’t as cumbersome as managing @Output properties back up the component chain.
So I guess to answer your question, it’s probably better to just pass @Input properties down to a dumb component but I wouldn’t say it’s an anti pattern to use a service