Changes for .NET 7 minimal API scaffolders

• Add whitespace route group definition and first API definition
• Remove all Produces extension method calls (they aren’t needed when using TypedResults or returning the object to be serialized directly)
• Remove all calls to WithTags from API definitions and instead have single call on the group definition
• Move call to WithOpenApi from group definition to API definitions (that method is designed to allow editing a specific OpenApiOperation so is more useful on the endpoint definitions directly IMO)
• Update non-EF Core scaffolder to also use TypedResults
• Question: Do we want to add an option for using strongly typed results?
  • My thinking is “yes” because they represent an alternate of writing the API but not necessarily a “better” way and some folks may prefer using Results and the Produces approach

[DamianEdwards]

Capturing feedback from meeting today:

• Make the database choice a drop-down list that’s only populated & enabled when a new data context class is being created. If an existing context class is selected, disable the drop-down list and make the selected item text like “Configured by DbContext”
• OpenAPI does not have a space in it
• Add tooltips to all labels/controls that describes in more detail what they do
• Default the “Use TypedResults” and “Enable OpenAPI” checkboxes to checked/true

[deepchoudhery]

All these have been addressed I believe, for anything else let’s use new(er) issues. Thanks.