Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Allow default_server_config as a fallback config #25682

Merged
merged 7 commits into from
Jul 10, 2023
Merged

Allow default_server_config as a fallback config #25682

Changes from 1 commit
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
f880422
Allow default_server_config as a fallback config
ShadowRZ Jun 29, 2023
b8b89b1
Doucment the fallback behavior
ShadowRZ Jun 29, 2023
8a49276
Update docs/config.md
ShadowRZ Jun 29, 2023
d9fb27d
Update
ShadowRZ Jun 29, 2023
8561f6f
Add tests
ShadowRZ Jun 30, 2023
7d79218
Add fallback code to mobile guide
ShadowRZ Jun 30, 2023
45421cb
Fix TypeScript lint errors
ShadowRZ Jul 8, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion docs/config.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,7 +46,9 @@ One of the following options **must** be supplied:
being optional.

If a combination of these three methods is used then Element will fail to load. This is because it is unclear which
ShadowRZ marked this conversation as resolved.
Show resolved Hide resolved
should be considered "first".
should be considered "first". However, if both `default_server_config` and `default_server_name` are used, Element will
try to look up the connection infomation using `.well-known`, and if that fails, take `default_server_config` as the
homeserver connection infomation.

## Labs flags

Expand Down