dansiegel / Mobile.BuildTools

The Mobile.BuildTools makes it easier to develop code bases in a clean, consistent, secure, and configurable way. Determine at Build which environment your app needs to run on, and what Client Secrets it should have. Plus many more amazing features!
http://mobilebuildtools.com
MIT License
228 stars 29 forks source link

Convert Secrets to AppSettings #262

Closed dansiegel closed 3 years ago

dansiegel commented 3 years ago

Description

This is a major change. Some care has been taken to try to keep the breaks to a minimum with an automatic conversion from the legacy Secrets to the new AppSettings. Note that this is not a simple change from secrets.json to appsettings.json, or from simply having a generated class go from Secrets to AppSettings.

There has been a schema change from projectSecrets to appSettings. Notably, a project can now have many configurations for generated classes. This may be useful for example if you want to generate say an OAuthSettings class and a ApiSettingsClass, etc, in the same project. This will be of more use in a future version of the Mobile.BuildTools once we switch to Roslyn Generation as this will give us the ability to implement interfaces.

Housekeeping

As part of the schema change, the Schema Generator has been reintroduced and the models more completely annotated to assist in an accurate and complete generation.

tinonetic commented 2 years ago

Hi there,

I am struggling to find documentation for this conversion from secrets.json to appsettings

Any help on where I can find it?

I see one of the samples is still using secrets.json

bricefriha commented 1 year ago

Thanks for the change @dansiegel, this seems great! I agree with @tinonetic, it would be nice to help us migrate our code to the new version. I have to keep 1.4 until I find a way to change the secrets.json.

If you explain it, I could maybe create a doc myself if you want 😉