Endpoint names are not inferred

[halter73]

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.

[captainsafia]

Endpoints can be given names in order to generate URLs to the endpoint.

This sentence feels a little confusing. What exactly are we trying to say here?

[halter73]

That endpoint names provide some indirection when generating links? I didn't write this originally, so I'm guessing. Do you have a suggestion for how we should reword this?

[mauler2025]

Providing the readers with a lot of examples makes it much clearer. :-)

var builder = WebApplication.CreateBuilder(args);

var app = builder.Build();

var users = new List<User>
 {
    new User(1,"A"),
    new User(2,"B"),
    new User(3,"C"),
 };

IResult GetUser(int id)
{
    return users.Find(u => u.id == id) is User user ?
        TypedResults.Ok(user) : TypedResults.NotFound();
}

IResult CreateUser(User user, LinkGenerator lg)
{
    users.Add(user);
    var path = lg.GetPathByName(nameof(GetUser), new { id = user.id })!;
    return TypedResults.Created(path, user);
}

var group = app.MapGroup("/users");

group
    .MapGet("/{id}", GetUser)
    .WithName(nameof(GetUser));

group.MapPost("/", CreateUser);

app.Run();

record class User(int id, string name);

[halter73]

Replaced by #27458.