Safia Abdalla
Safia Abdalla
@RachitMalik12 Can we slot this in for v2? I don't think we necessarily have to change anything about the in-memory model to support sorting but the serialization step should attempt...
> Please don't reorder these. They represent something functional that users care about. For example: This isn't about reorder properties on schemas. It's about ordering in the for top-level items...
@bkoelman Happy to review a PR to update the nullability annotations and react to them here.
@CaringDev Thanks for filing this issue! At the present moment, the `ModelMetadata` APIs that are used by the `ApiExplorer` to represent the parameter binding behaviors of type _do not_ expose...
> I'd like to point out that this also affects other projects that build on top of the ApiExplorer like Swashbuckle so fixing this would be helpful for the greater...
Exposing the property-to-parameter mapping effectively provides a shortcut for the parameter to property lookup that you're currently doing in your code. The benefit is that the property-to-parameter mapping provides richer...
> Yes, that's a big blocker. OpenApiSchemaService.GetOrCreateSchemaAsync is internal, we need to be able to override this. Not everything can be done afterward from options.SchemaTransformers. Yep, this point is heard....
@dorlandode Thanks for filing this issue! Quick note: The Aspire + Azure Functions currently requires that you use a .NET 9 SDK. Does this issue repro for you in both...
> dotnet sdk 8.0.309 I noticed that you are using the 8.0 SDK here. Can you reproduce these issues with the .NET 9 SDK?