You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, profiles and many of our default config values are written to the config. Unfortunately, this makes it hard for us to change them for existing users, even when the user hasn't explicitly chosen to override something.
Proposal:
Mostly empty on-disk config by default.
Add a "profiles" section to the config that lists all the profiles that should be applied and in what order.
Add "DefaultX: bool"/"CustomX: value" options where applicable (e.g., bootstrappers), to allow users to extend defaults.
At runtime, we'd:
Read the config.
Apply the defaults to the in-memory config.
Apply the profiles to the in-memory config.
When updating the config, we'd:
Re-read the on-disk config.
Apply the update to the on-disk config without persisting the in-memory config (unless necessary?).
The text was updated successfully, but these errors were encountered:
Currently, profiles and many of our default config values are written to the config. Unfortunately, this makes it hard for us to change them for existing users, even when the user hasn't explicitly chosen to override something.
Proposal:
At runtime, we'd:
When updating the config, we'd:
The text was updated successfully, but these errors were encountered: