Nested Editor Null Reference Exception. Fix a bug in the HtmlFieldPrefix.cs:23 by sgarnovsky · Pull Request #58888 · dotnet/aspnetcore (original) (raw)
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters
[ Show hidden characters]({{ revealButtonHref }})
Actually, a null reference exception occurs when a nested Editor.NameFor() or child component based on InputBase is used. The referenced bug issue has a sample to reproduce this problem.
The fix is a quite simple and probably doesn't require any test unit as an original issue looks like an indexing reference misprint.
It will fix #53956
This a fix for nested Editor described in this issue: dotnet#53956
this may need backports to 8 and 9
cc @javiercn
Azure Pipelines successfully started running 1 pipeline(s).
captainsafia pushed a commit that referenced this pull request
This a fix for nested Editor described in this issue: #53956
this may need backports to 8 and 9
cc @javiercn
I see a fix has been applied in the .Net 10 preview 2. It is very good.
Unfortunately, it is not in the .Net 8 or .Net 9 the latest SDK releases.
I just got a need to use nested Editor components but I can't migrate a production project to use the .Net 10 preview (it doesn't look as a safe option).
Is there any possibility to include this fix in one of the next release of .Net 8 and .Net 9?
Actually, it will be better to place it in both... to fix this minor issue to open Blazor forms for more flexible implementations in these versions too.