DaveRMaltby

@SaadAlyah, thank you for mentioning this. I would also appreciate it if you would submit a PR or create a fork with the changes. Thank you!

I've provided a solution. Please let me know if there is anything more needed on my end. Thanks!

I have a need to create many EF Core providers and decided to create a template repo for this purpose. It is still a work in progress (i.e. need to...

> @DaveRMaltby I do think we skeleton/template provider is a good thing to have, as a starting point for people writing providers. > > Some specific points come to mind...

Created PR #15 to solve this issue.

I understand your concern and have the same concerns in mind too. With this issue having so many touch points into your codebase, I held back on trying to do...

Thank you sir! Looks like a great workaround that should let my project return to using your NuGet packages (instead of a fork). Appreciate it! I was unaware about the...

For anyone desiring this feature, here's a possible alternate solution to this feature request, I made [a basic pushbutton style example](https://try.mudblazor.com/snippet/mYwwbwwkqIwXgUoH) that acts like it is one control.

I've tracked down the issue. Although in v13 the default value is still in the definition for this field that uses the DefaultValue attribute, turns out that the `Optional.From()` method...

If an overload of `From()` method is needed, then for reference, the `From` is setup (in a System.Linq.Expressions.Expression) to be called at https://github.com/ChilliCream/graphql-platform/blob/main-version-13/src/HotChocolate/Core/src/Types/Utilities/Serialization/InputObjectCompiler.cs#L318