Skip to content

Add way to create a WebApplication without the defaults #37

Open

Description

@davidfowl

Maybe we need 2 overloads:

  • WebApplication.CreateBuilder - Less stuff? console logger and no configuration providers.
  • WebApplication.CreateDefaultBuilder - What we have today

OR do we do nothing and require users to clear logging and configuration providers.

Activity

  1. thenameless314159 commented on Mar 2, 2021

    @thenameless314159

    No configuration provider for the CreateBuilder overload ? This won't take any string[] args then ?

    I don't think my opinion is required but both would be good, maybe expose an extension method to clear both providers and make an overload that call it after creating the builder instead of an almost empty builder ?

  2. davidfowl commented on Mar 2, 2021

    @davidfowl
    CollaboratorAuthor

    I'm worried about the choices. Too many choices would confuse people so what the defaults are and what are in them need to be intuitive.

  3. thenameless314159 commented on Mar 2, 2021

    @thenameless314159

    I see, since feather aim to provide more straightforward webhost building logic you can't expect people to knows what the aspnetcore WebHost.CreateDefaultBuilder() does (since the default feather webhost make rather similar registrations if I'm not mistaken) ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions