Blazor DynamicComponent

[daveabrock]

Good morning,

I'm not sure your timeline in documenting the DynamicComponent released with .NET 6 Preview 1, but I can lend a hand if you'd like (I wrote about it just now and it seems to be straightforward).

[guardrex]

We usually hold off a bit on new coverage because ...

• PU churn in the past has caused problems: Before features settle into a close-to-final form, we end up having to revise docs (sometimes more than once) during the preview/RC phase. It's generally been less costly 💰 to wait a bit longer. Things don't change much at or after RC1 ... usually 🤞.
• I've been very busy with UE passes, so it's just as well. If I had to sweat a lot of 6.0 coverage right now, it would have radically slowed down the UE passes, which are desperately needed imo.
• Also, we haven't had major time crunches documenting a release when starting most of the coverage just before or at RC1's release. It's especially been the case because PU engineers provide a lot of the content, so I have material to edit and polish up for the coverage. I haven't had to draft a lot of content from scratch each release. We usually get ... er ... say 90% (or more) in place for the GA.

Yes ... AFAIK, you're welcome to provide the content. Let me get back to you later today on location for it. I'm ⛏️⛰️😅 right at the moment. I'll get back to u soon. 🏃

[guardrex]

Still buried in work ... let me get back to you @daveabrock early next week. 🏃🏃🏃🏃🏃🏃😅

[daveabrock]

Appreciate the follow-up ... no rush on my end. Just putting it out there, and makes sense with the timing as it's still early. It can wait.

[guardrex]

Ok ... I'm BACK. There are two ways to go ...

• Section in the Components overview topic: It would have to be considerably shorter (text and example) than what's in your post. The example would probably roll both with and without params. It would probably be more bare bones, similar to what DR did in the blog post ... minimal example code ... quick explanation.
• New topic: Could be long and written out similar to your post with the larger example and separate section for optional params. You can use your post text as the basis of the whole thing if you like.

I don't have a preference between those two options. I'll leave it up to you.

WRT sample code, I'll leave it up to you on whether or not it goes into the topic (triple backtick code blocks) or into the new snippet sample apps. I can always roll the code from the topic into those apps later, which would simplify what you need to do. I'll provide more guidance depending on your decision.

WRT metadata and whatnot, let me know which approach you prefer for coverage ☝️. I'll provide more guidance based on your decision.

Note that I'm working on the Components overview topic this week, so I recommend holding off on a PR that touches it until after I'm done and have merged the UE pass on it. I anticipate having it wrapped up by Friday afternoon.

[guardrex]

btw - I'm going to ping Artak and DR offline to ask about location for this. If they don't respond, we'll go with your preference.

I/we should hear back by the end of the week. Best to hold off on proceeding for now. I also need to provide doc layout/location/metadata/content nits, bits, tidbits, morsels, crumbs, nibbles, dabs, pinches, and slivers ..... and other small things 😁. I'll write it out after we hear back.

[guardrex]

We'll also get an answer on dotnet/aspnetcore#31754 before proceeding here.

[daveabrock]

Personally, I would prefer the second approach. I've already got most of the content and I think the parameters section should help iron out some lingering questions.