Consider extensions for Minimal API

[TWolversonReply]

I'm giving this project a first look just now, and it seems promising.

One thought that occurred to me was that the typical structure of Minimal API projects fairly closely mirrors the structure expected by the APIOps tooling, for obvious reasons. Each method roughly corresponds to an operation, each MapGroup roughly corresponds to an API.

Would it make sense to have an option to define the IDocument method bodies as extensions to Minimal API action methods? This would allow you to express the desired proxying configuration to support calling your API from the outside world within the API, as opposed to defining them in separate classes.

Given a code example lifted from the documentation:

<snip>

app.MapGet("/todoitems/{id}", async (int id, TodoDb db) =>
    await db.Todos.FindAsync(id)
        is Todo todo
            ? Results.Ok(todo)
            : Results.NotFound());

<snip>

Suppose we add:

<snip>

app.MapGet("/todoitems/{id}", async (int id, TodoDb db) =>
    await db.Todos.FindAsync(id)
        is Todo todo
            ? Results.Ok(todo)
            : Results.NotFound())
      .WithInboundPolicy(() => {
          // method implementation equivalent to IDocument.Inbound for an operation
      });

<snip>

Naming and factoring obviously open to discussion.