aspnetcore
aspnetcore copied to clipboard
Fix DictionaryModelBinder null reference issue
Fix https://github.com/dotnet/aspnetcore/issues/45502
@dotnet/minimal-apis can you please review it 🙏.
@dotnet/minimal-apis can you please review it 🙏.
~LGTM under the assumption that I think I've grokked the changes in
DictionaryModelBinder
after some conversations with @brunolins16 and they seem sensible.~LGTM -- @brunolins16 and I went through this in person today.
I will merge but wait to see the behavior in Preview 1 to start the backport.
@brunolins16 Thanks for taking care of this! Will this also be merged to aspnetcore 7? or should we skip 7 and wait for aspnetcore 8?
Hi @tomer-amir. It looks like you just commented on a closed PR. The team will most probably miss it. If you'd like to bring something important up to their attention, consider filing a new issue and add enough details to build context.
@brunolins16 Thanks for taking care of this! Will this also be merged to aspnetcore 7? or should we skip 7 and wait for aspnetcore 8?
@brunolins16 referenced our backport approach in his original comment. We'll backport after we've validated the fix in .NET 8. If you'd like to help out, you can try out an upcoming nightly release (see this repo) and verify if the behavior that we changed meets expectations.
You can read more about how we do backports in this doc.
Hi @brunolins16 Will this be backported on 7.0 ? we have this problem with current .net 7 version :/ Thank you
Hi @Jsl-1. It looks like you just commented on a closed PR. The team will most probably miss it. If you'd like to bring something important up to their attention, consider filing a new issue and add enough details to build context.
Hi @brunolins16 Will this be backported on 7.0 ? we have this problem with current .net 7 version :/ Thank you
Hi @Jsl-1! We typically backport issues that are high priority and don't have easy workarounds in existing languages. Given the .NET 8 release is right around the corner, I'm less inclined to backport this issue.
Hi @brunolins16 Will this be backported on 7.0 ? we have this problem with current .net 7 version :/ Thank you
Hi @Jsl-1! We typically backport issues that are high priority and don't have easy workarounds in existing languages. Given the .NET 8 release is right around the corner, I'm less inclined to backport this issue.
Ok, thank you. we manage to make a dirty workaround. It can do the job waiting for the release.
Hi @Jsl-1. It looks like you just commented on a closed PR. The team will most probably miss it. If you'd like to bring something important up to their attention, consider filing a new issue and add enough details to build context.