I think i agree with both <@!137108238880473088> a...
# package-development
I think i agree with both @User and @User - keeping the config inside the existing options system of .net core gives you all the power and flexibility that comes with it, (env variables, key vaults etc), but i can see it getting messy, and people might want to move their config out. I am coming around to thinking this should be the choice of the site dev, but it should be something package devs can easily support. (why i think i am just going to ship an extension method to make it easy to move).