Skip to content

Commit a84349f

Browse files
authored
Deprecate camelCase config options (#25800)
1 parent b89b000 commit a84349f

File tree

1 file changed

+8
-0
lines changed

1 file changed

+8
-0
lines changed

docs/config.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,13 @@
11
# Configuration
22

3+
### 🦖 Deprecation notice
4+
5+
Configuration keys were previously a mix of camelCase and snake_case.
6+
We standardised to snake_case but added compatibility for camelCase to all settings.
7+
This backwards compatibility will be getting removed in a future release so please ensure you are using snake_case.
8+
9+
---
10+
311
You can configure the app by copying `config.sample.json` to `config.json` or `config.$domain.json` and customising it.
412
Element will attempt to load first `config.$domain.json` and if it fails `config.json`. This mechanism allows different
513
configuration options depending on if you're hitting e.g. `app1.example.com` or `app2.example.com`. Configs are not mixed

0 commit comments

Comments
 (0)