dotnet/aspnetcore

Is there an existing issue for this? I have searched the existing issues Describe the bug When writing more than 32K of data to local storage, and then reading it, a circuit deadlock occurs, and all operations cease to execute on the circuit. It is unclear what is happening and a warning should instead be presented to the user. Expected Behavior Instead of freezing and a deadlock, a warning/error should be presented to the developer so they know what is occurring, and how to fix it. Steps To Reproduce Run the following reproduction: https://github.com/Mike-E-angelo/Stash/tree/master/Blazor.MessageLimit Press the first button Press the 2nd button Observe circuit deadlock Uncomment this line to fix the issue: https://github.com/Mike-E-angelo/Stash/blob/master/Blazor.MessageLimit/Program.cs#L12 Exceptions (if any) None, that's what this request is for .NET Version 10.0.301 Anything else? Thank you for all your great and amazing work on Blazor. 🙏

Summary When setting component parameters directly compile time analysis will find mismatched types and provide a helpful error message pointing to the exact position of the problem with the type cast failing. If instead a developer splats attributes onto the component then a mismatched type will only be caught at runtime during ParameterView.HasParameterChanged() which results in an unhelpful error message stating that types could not be converted (e.g. could not convert from Int32 to Double) but does not provide the name of the parameter or calling component. Motivation and goals Vague error messages at runtime are confusing and upsetting to the best developers, adding a type check and providing some more specific information will aid in tracking down specific attributes causing issues without having to comb through every component and splat in use on a page. In scope Developer splats attributes onto a component, the type of an attribute does not match: the developer should receive a

Is there an existing issue for this? I have searched the existing issues Is your feature request related to a problem? Please describe the problem. I am trying to generate openapi documents using the new XML comment feature in .net10 https://learn.microsoft.com/en-us/aspnet/core/fundamentals/openapi/openapi-comments?view=aspnetcore-10.0 My issue it that the example is added under an "example" field under the "schema" key. And form what I can read in the openapi spec that field is deprecated. This becomes an issue for me when I try to import my openapi spec into the API-gateway solution we use at my organization. This is what my code generates today with Microsoft.AspNetCore.OpenApi version "10.0.2" : current.json Describe the solution you'd like I would like it to generate something like this: target.json Additional context https://spec.openapis.org/oas/v3.1.1.html#working-with-examples https://spec.openapis.org/oas/v3.1.1.html#schema-object