element-hq / element-hq/element-web

all user-settings should be manageable within config.json

Open
#23,129 1 comment 0 reactions 0 assignees View on GitHub
O-Uncommon T-Enhancement X-Needs-Product
Dominant language
TypeScript
Stars
13.5k
Forks
2.8k
PR merge metrics
PR metrics pending

Description

### Your use case

In my opinion the most options (especially: sendReadReceipts) in user settings should be preset in config.json.

The values should be:
* `force_true`: can't be disabled by user
* *true`: user can disable this option, this setting is enabled by default
* `false`: user can enable this option, this setting is disabled by default
* `force_false`: can't be enabled by user

### Have you considered any alternatives?

To leave the existing boolean logic untouched, the force settings (`settingForceDefaults`) can be separated:

fe:
```json
{
"settingDefaults": {
"breadcrumbs": true,
"UIFeature.urlPreviews": false
},
"settingForceDefaults": {
"UIFeature.feedback": false
}
}
```

### Additional context

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.