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.
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
Fix for the #1865 #1889
Fix for the #1865 #1889
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks plausible to me, but it's a shame we're directly duplicating the definitions from api/client-server/definitions/push_ruleset.yaml
etc. @turt2live: do you know if there is a way these could be shared to save duplication?
Using |
Ah yes. there are plenty of examples of APIs which refer to event schemas. @ma1uta: could you rework this to remove the duplication? |
@richvdh done. |
A changelog (clarification) and this is ready to merge, I guess :) |
@richvdh @turt2live @KitsuneRal done. I hope this is enough to merge :) |
Lots of green checkmarks compels me to merge this. Thanks for the PR! |
Add the m.push_rules schema.
It needs to check carefully the schema.
Signed-off-by: Anatoly Sablin sablintolya@gmail.com