A plea for more documentation #51275
Unanswered
DavidThielen
asked this question in
General
Replies: 1 comment
-
@danmoseley should this be moved to https://github.com/dotnet/AspNetCore.Docs? Or please route it to where it belonds. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi;
I know documentation is a really hard problem that seems never ending. And having been CEO of a software company I understand why it's never going to be complete. And... I do think the documentation that exists is well written (98% of the time) and generally complete.
But with that, there's a dire need for documentation on issues where there is presently silence. The specifics I've hit recently (all Blazor server):
Task.Yield()
inOnInitializedAsync()
will then let you access@ref
variables. What we need is guidance here. An authoritative answer of either this will always work or very bad idea. Either answer is fine, but let us know. Especially as, if it's a bad idea and will fail in the future, we're going to see a lot of web sites die on an update that does this.ObjectGraphDataAnnotationsValidator
is buggy and never going to be part of a release, so be it. But please, a web page telling us how to handle validation for use cases beyond the simplistic.For the above cases, and I'm assuming similar questions, we're asking what approach to take so our code will work not just now, but in future versions. Because with all of us guessing, you know a fair amount of the code being written today will break in a future release. Or even worse, some bad practice has become so widespread, you have to support it which constrains future versions.
To reiterate, I think Blazor is a very well designed and implemented system as well as rock solid.
thanks - dave
Beta Was this translation helpful? Give feedback.
All reactions