6 ms·

> Have a reasonable developer tell me what a component viewProvider is and how it’s different from a provider using the @Component docs. It’s impossible. https:

> Have a reasonable developer tell me what a component viewProvider is and how it’s different from a provider using the @Component docs. It’s impossible. https://angular.io/api/core/Component#viewProviders https://angular.io/api/core/Component#viewProviders Like this? - https://angular.io/guide/hierarchical-dependency-injection#using-the-viewproviders-array https://angular.io/guide/hierarchical-dependency-injection#u... - (new docs site) https://angular.dev/guide/di/hierarchical-dependency-injection#using-the-viewproviders-array https://angular.dev/guide/di/hierarchical-dependency-injecti...

miiiiiike 2y ago
Exactly my point. I linked to the reference docs, you linked to the usage docs. They're completely divorced from each other. There's not even a link from reference to usage docs. For the reference docs to be useful you already have to know what the thing is, what it does, why you'd need it. You can be on the component page where `viewProviders` is documented and get nothing from it if you're coming in fresh. Why would ever design docs like that? Angular is the only framework I've ever struggled to learn. It's a complicated framework but that's not the problem. The docs are the problem.
- pohuing 2y ago
  Which is strange. Google knows how to write docs. Or at least I've been very happy with the flutter docs. But now working on angular frontend is awful tooling wise. I don't even get useful inline docs for a lot of libraries.
  - troupo 2y ago
    > Which is strange. Google knows how to write docs. Oh, they don't. Some of their teams know how to write docs for some of the products. A lot of the time it's autogenerated reference with a couple of bare-bones examples
- deleted 2y ago
  [deleted]
- scroll-break 2y ago
  First, create an AnimalService with an emoji property of whale You can leave all the FlowerService related code in place as it will allow a comparison with the AnimalService.
- hmcdona1 2y ago
  Yeah it’s not great, but they do both show up as results via search.

miiiiiike 2y ago

Exactly my point. I linked to the reference docs, you linked to the usage docs. They're completely divorced from each other. There's not even a link from reference to usage docs. For the reference docs to be useful you already have to know what the thing is, what it does, why you'd need it. You can be on the component page where `viewProviders` is documented and get nothing from it if you're coming in fresh. Why would ever design docs like that? Angular is the only framework I've ever struggled to learn. It's a complicated framework but that's not the problem. The docs are the problem.

pohuing 2y ago
Which is strange. Google knows how to write docs. Or at least I've been very happy with the flutter docs. But now working on angular frontend is awful tooling wise. I don't even get useful inline docs for a lot of libraries.
- troupo 2y ago
  > Which is strange. Google knows how to write docs. Oh, they don't. Some of their teams know how to write docs for some of the products. A lot of the time it's autogenerated reference with a couple of bare-bones examples
deleted 2y ago
[deleted]
scroll-break 2y ago
First, create an AnimalService with an emoji property of whale You can leave all the FlowerService related code in place as it will allow a comparison with the AnimalService.
hmcdona1 2y ago
Yeah it’s not great, but they do both show up as results via search.