Override InputNumber type attribute

[guardrex]

Fixes #33556

Mackinnon ...

• This covers both the 9.0 What's New article and the new section in the Input Components article.
• Sorry that I replaced your example. I'm trying to go with Star Trek-themed forms throughout the Forms node.
• Is there anything else that we need to tell devs in the article section?

---

Internal previews

📄 File	🔗 Preview link
aspnetcore/blazor/forms/input-components.md	ASP.NET Core Blazor input components

[MackinnonBuck]

I appreciate the new example - it's more fun than the one I drafted up 🙂

However, I'm wondering if we should keep the docs for this feature a bit shorter. Overriding the type attribute on InputNumber is a pretty niche scenario that can likely be mentioned in passing rather than getting a section dedicated to it. Do you agree? I appreciate that it's a cool example, I'm just worried that it could make the docs a bit noisy when we're mostly trying to highlight the line(s) with <InputNumber type="range" />.

[MackinnonBuck]

e.g., we could even just have a note somewhere like:

Note

The <InputNumber> component can also act as a range input by adding the type="range" attribute.

[guardrex]

I suppose so. We don't have a dedicated section for InputNumber, so I didn't have much choice if we wanted a full sample.

I'll see about knocking it down to something simple in the main coverage, and then I'll place a reduced full example component in the What's New coverage ... Star Trek, of course! 😆

[guardrex]

Nevermind ... I had time now to adjust it before leaving. Try it now.

[guardrex]

Ok ... I'm done mess'in around with it. 😆

[guardrex]

@MackinnonBuck ... See if that (finally 🙈) gets it.

I have 🍺 in the fridge. Maybe I need to drink one ............ or FIVE! 😆

[MackinnonBuck]

Looks great!