Blazor form component InputSelect should support binding of type Guid

Is your feature request related to a problem? Yes.

Following code does not work if binding Type is Guid. The runtime error in browser console is `InputSelect does not support the type Guid"

// ItemCreate.razor
...
<InputSelect bind-Value="Item.CategoryId">
  @foreach(var cat in Categories) {
    <option value="cat.Id">@cat.Name</option>
  }
</InputSelect>
...

// Entities.cs
...
public class Item
{
  public Guid Id { get; set; }
  public string Name { get; set; }
  public virtual Category Category { get; set; }
  [ForeignKey("Category")]
  public Guid? CategoryId { get; set; }
}

public class Category
{
  public Guid Id { get; set; }
  public string Name { get; set; }
}
...

Describe the solution you’d like

InputSelect should support binding for type Guid.

Describe alternatives you’ve considered

I have to create custom MyInputSelect on top of InputSelect which supports Guid.

Additional context

Asp.Net Core 3 Preview 4 Browser: Chrome @version:73

[cmoncure]

Guid (or UUID) is used by every modern web app on the face of the planet. It should have first class support everywhere it’s possible to use it.

Currently this has to be worked around by adding redundant properties to your model and explicitly invoking Convert on the getter and setter every time you want to use InputSelect based on an object’s Guid.

`

class Model : MyObject 
{
    public string MyUidAsString { get; set; }

    override public Guid MyUid
    {
        get { return Guid.TryParse(MyUidAsString, out Guid g) ? g : default; }
        set { MyUidAsString = Convert.ToString(value); }
    }
}

`

This is frustrating and tedious. Not Blazing!

[Eirenarch]

I am really curious about the thought process behind only supporting string and enum. It is obvious to me that the integer types, guid and their nullable versions should also be supported