65d6bfe6e9
* inline call to `SettingsStore.isEnabled` * Remove confusing `SettingsStore.isEnabled` This was basically the same as `SettingsStore.canSetValue` only more confusing, so let's get rid of it. * Add `configDisablesSetting` value for Settings The current magic where this only works for features (but not beta features!) is, well, magical. And I need more flexibility here. * Remove redundant levels constant `LEVELS_FEATURE` I don't know if this was ever intended to have different semantics to `LEVELS_DEVICE_ONLY_SETTINGS_WITH_CONFIG`, but if it was, those semantics shuold have been written down. They now seem to be used entirely interchangably. |
||
---|---|---|
.. | ||
__snapshots__ | ||
account | ||
devices | ||
discovery | ||
notifications | ||
shared | ||
tabs | ||
AddPrivilegedUsers-test.tsx | ||
AvatarSetting-test.tsx | ||
ChangePassword-test.tsx | ||
CrossSigningPanel-test.tsx | ||
CryptographyPanel-test.tsx | ||
EventIndexPanel-test.tsx | ||
FontScalingPanel-test.tsx | ||
JoinRuleSettings-test.tsx | ||
KeyboardShortcut-test.tsx | ||
Notifications-test.tsx | ||
SecureBackupPanel-test.tsx | ||
SettingsFieldset-test.tsx | ||
ThemeChoicePanel-test.tsx |