-
-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Convert Secrets to AppSettings #262
Conversation
71a49b2
to
ca1c2a4
Compare
ca1c2a4
to
bcece6a
Compare
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 |
Thanks for the change @dansiegel, this seems great! If you explain it, I could maybe create a doc myself if you want 😉 |
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
toappsettings.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 aApiSettingsClass
, 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.