Endpoint names are not inferred #27424
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This was the behavior in some .NET 6 preview releases, but was reverted in .NET 6 RC 2 due to potential uniqueness issues given overloaded method groups: dotnet/aspnetcore#36518. This is why
{linker.GetPathByName("Hi", values: null)}
was null.It's surprising that this REVIEW note stayed in the doc for over a year without anyone who knows about this noticing, but that's partially on me.
Also, these are technically "endpoint" names, not "route" names.