Update comments in settings logic (#12148)
Follow-up on https://github.com/matrix-org/matrix-react-sdk/pull/12125pull/28217/head
parent
79f2c9749b
commit
dfebd59629
|
@ -127,9 +127,9 @@ export interface IBaseSetting<T extends SettingValueType = SettingValueType> {
|
|||
/**
|
||||
* If true, then the presence of this setting in `config.json` will disable the option in the UI.
|
||||
*
|
||||
* In other words, we prevent the user overriding the setting if an explicit value is given in `config.json`;
|
||||
* though note that users who have already set a non-default value before `config.json` is update will continue
|
||||
* to use that value (and, indeed, won't be able to change it!)
|
||||
* In other words, we prevent the user overriding the setting if an explicit value is given in `config.json`.
|
||||
* XXX: note that users who have already set a non-default value before `config.json` is update will continue
|
||||
* to use that value (and, indeed, won't be able to change it!): https://github.com/element-hq/element-web/issues/26877
|
||||
*
|
||||
* Obviously, this only really makes sense if `supportedLevels` includes {@link SettingLevel.CONFIG}.
|
||||
*/
|
||||
|
|
|
@ -528,7 +528,8 @@ export default class SettingsStore {
|
|||
return false;
|
||||
}
|
||||
|
||||
// When non-beta features are specified in the config.json, we force them as enabled or disabled.
|
||||
// For some config settings (mostly: non-beta features), a value in config.json overrides the local setting
|
||||
// (ie: we force them as enabled or disabled).
|
||||
if (SETTINGS[settingName]?.configDisablesSetting) {
|
||||
const configVal = SettingsStore.getValueAt(SettingLevel.CONFIG, settingName, roomId, true, true);
|
||||
if (configVal === true || configVal === false) return false;
|
||||
|
|
Loading…
Reference in New Issue