5 ms·
> I think the main limitation of our docs is that it mostly explains what the pieces do, not how to use them to achieve a particular goal I honestly prefer thi
by Rapzid 3y ago
> I think the main limitation of our docs is that it mostly explains what the pieces do, not how to use them to achieve a particular goal
I honestly prefer this type of documentation. ASP.NET Core has the complete opposite problem where it's too example based.
- F-W-M 3y agoFor many things it's simple enough to read the code, did this e.g. for the Configuration system in ASP.NET Core. Dunno, if I could do this with postgres.
- Rapzid 3y agoYeah you'll end up reading the source code regardless if it's simple or not though haha. I've had to read through tons of the Identity and Auth code to get a handle on how to integrate with it and there are TONS of interfaces, implementations, and etc you have to cross-reference and hunt down to start building a mental model. You don't even get a diagram in the docs explaining how all the different filters and crap tie together(on top of auth having ITS OWN MIDDLEWARE PIPELINE) lol. Combine that with maybe the info you are looking for actually is in the docs, but it's sprinkled across loads of examples so it's hard to find or build a comprehensive understanding of.