Kevin Krumwiede

I'm just including EJML as a dependency. The heavy handed solution is to disable lint. This isn't a big problem for me, more of a suggestion for improving the library.

@justcla I can frequently repro this when trying to restore `material-design-icons`, which contains a large number of files. It fails on a different file every time. It seems that restore...

Calling `Required()` does not change the metadata. Calling `Optional` *does* change the metadata by adding this annotation: ```XML ``` So it seems that parameters are required by default. My controller...

My general expectation for what required means was set by [Model Validation in ASP.NET Web API](https://docs.microsoft.com/en-us/aspnet/web-api/overview/formats-and-model-binding/model-validation-in-aspnet-web-api). Overposting does not cause the model state to be invalid; unexpected properties are ignored....

I got the behavior I wanted with this controller action signature: `public IActionResult UnboundAction([Required, FromForm] string foo, [Required, FromForm] string bar)`. If I remove `Required` so the Swagger UI allows...

@xuzhg The names of unbound actions don't seem to matter. It's only recognized as an OData route if I decorate it with `[HttpPost($"/{EntityDataModel.RoutePrefix}/{nameof(UnboundAction)}")]`. In what way is `public IActionResult UnboundAction([Required,...

Correction: although the signature with separate `FromForm` parameters allows me to achieve what I want, it does not entirely work as expected. I just noticed that I forgot to remove...

Conventional routing won't detect it. But if you use explicit attribute routing (which AFAIK you must always do for unbound actions anyway) the route is listed as an OData route...

To be clear, I'd prefer to use `ODataActionParameters` if there's a way to make it treat required parameters as required. I'm looking at [`ODataBodyModelBinder`](https://github.com/OData/AspNetCoreOData/blob/69eec03c7003fe12d92cdc619efdc16781683694/src/Microsoft.AspNetCore.OData/Formatter/ODataBodyModelBinder.cs)...

I think the issue is in `ODataActionPayloadDeserializer`. It iterates over the properties that are found in the payload and looks up the corresponding `IEdmOperationParameter`. This is backward. It should iterate...