Enable new Cody Web by default#63493
Conversation
|
Wait, why can't we set a global setting for dotcom? |
|
@camdencheek Dotcom uses files to set initial site and global settings, if you try to go to dotcom and change the configuration it will throw a warning that these settings were created from a file and hence can't be edited (we build dotcom with
|
|
Right, I we should be changing this setting there (in the file), not manually overriding it in the frontend. Otherwise, will this actually be overrideable? |
This is correct, since this package Cody Web is experimental I want to have a flow where you can go back to the old Cody Web in case if some users will have problems with new one. |
|
Yep, that still works with global settings. User settings cascade with higher priority than global settings. |
|
Not a big deal though, so let's not worry about it 🙂 |
This PR turns on the new Cody Web by default for everyone. It's still possible to opt-out to the old Cody Web with
"newCodyWeb": falsein your experimental features in settings.I forgot that the dot com instance seeds its global settings and site configuration from files and
doesn't allow us to override specific settings there;
Test plan