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
we want users to be able to use sonnet the same way they have since they first got it, that means not adding breaking changes on the user interfaces and not having configs that change the behavior of sonnet
this leaves us with the problem of old behavior being objectively worse, and we want new users to be able to have the nicer defaults
the solution: stable vs unstable config option set-config-stability [stable|unstable] should set the stability of sonnet configs, unstable will enable new features that should be on by default while stable will not change the behavior of sonnet after a config is made, this formalizes what was an unspoken rule in sonnet
The text was updated successfully, but these errors were encountered:
questions should be raised on how to implement this, as configs are all set to a single fallback default, potentially conf_cache could be overridden with an identical default set for that guild, only with option parameters tweaked
we want users to be able to use sonnet the same way they have since they first got it, that means not adding breaking changes on the user interfaces and not having configs that change the behavior of sonnet
this leaves us with the problem of old behavior being objectively worse, and we want new users to be able to have the nicer defaults
the solution: stable vs unstable config option
set-config-stability [stable|unstable]
should set the stability of sonnet configs, unstable will enable new features that should be on by default while stable will not change the behavior of sonnet after a config is made, this formalizes what was an unspoken rule in sonnetThe text was updated successfully, but these errors were encountered: