Jan Jansen
Jan Jansen
At the time we integrate ruma-client-api, we should think of sharing `Endpoint`.
The orignal idea was to add a function to the main. This function generate at a given position a sample config with example values. The advantage of this is automate...
Currently easy issues are #39 #40 or the filter API. You could use my Rust struct for filter. See in my PR for sync.
If you need any support, you could ask me on Martix same Name.
@mujx Do you like to rebase. I'm back with some time to work on ruma.
I think of the following `if creation_options.initial_state.is_some() {`.
Moving part in into private function would help reduce doubling, but make it much easier to read since every function has a name and a small doc.
For example: https://github.com/ruma/ruma/blob/master/src/api/r0/profile.rs#L340 and https://github.com/ruma/ruma/blob/master/src/api/r0/profile.rs#L361 are nearly the same test. We could write one macro to represent both and then generate these tests
https://github.com/matrix-org/synapse/blob/fad3a8433535d7de321350bbd17373138c6fd3ec/synapse/rest/client/v1/voip.py You need to extend the config.
#106