V02460

If I could make a wish here, it would be making the saturating constructors public.

@MadLittleMods: Could you clarify what you want the error message to be? For these PRs I did not use my own wording, but took it from `registration_shared_secret`: https://github.com/element-hq/synapse/blob/aab3672037ee9ea71c54c89c86d9c0cc35ae184f/synapse/config/registration.py#L37-L40

Nice to see you involved, I’m really glad you’re going with this MR! :) > - suspicious defaults > - public_baseurl One important lesson I learned since starting with schemas...

> The config documentation generation should be checked in CI — to make sure the schema is valid and that the doc doesn't fall out of sync by accidental manual...

I looked into how to properly handle the meta stuff of JSON Schemas. Because of the custom `io.element.*` keywords, a custom vocabulary must be defined – I went with the...

Updated the patch set: - Incorporate the latest documentation updates. - Remove the JSON version of the schema as YAML is sufficient for this usecase. - Add CI support to...

Updated the branch to latest develop. Can we try getting this in shape and merged?

Fun Fact: To get IDE support in VS Code for any Synapse config, you can add the following line to the start of the file right now: ```yaml # yaml-language-server:...

> Alternatively, we don't do this internally but instead expose PgEscapeOption and direct people to use it. That would be backwards-compatible. This would leak implementation details and keep a foot...

Thank you for replying! Sadly, the given suggestions all don’t work. They fail for cases of a template not producing a document: 1. ``` DocumentIndex: 0 Expected to contain document:...