ASP.NET Core updates in .NET 11 Preview 6 #67788
Replies: 2 comments 1 reply
|
It's a fantastic capability to be able to scroll to a specific position using the Blazor Virtualize component. |
|
Hi @danroth27, Small concern with the [UniqueEmail / async validation] example. Between IsValidAsync and the actual INSERT, a concurrent request can register the same email — so the validation passes but the insert still races. The real guarantee has to come from a DB unique constraint + business layer anyway, making the attribute check redundant in a validation step. It fits better as a 409 Conflict from the service layer than a 400 from validation. A more fitting example might be checking a code against a reference/master-data table (country ISO code, currency code, etc.). That data is stable, the check is idempotent. etc (something like that ?) The feature is great but people will maybe use it weirdly because of this example... |
|
Thanks @fdonnet. You're right that async validation can't guarantee uniqueness on its own. A DB unique constraint still has to be the real safeguard. The sample is meant to show the mechanics of async validation, and the check is more of a UX affordance: it returns a friendly field-level error in the common case. Maybe a different example would've been better, but I still think the current one is valid. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Here's a summary of what's new in ASP.NET Core in this preview release:
ASP.NET Core updates in .NET 11:
All reactions