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.

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

Additional keys in GET /capabilities don't have to be objects #1945

Merged
merged 2 commits into from
Sep 11, 2024

Conversation

Johennes
Copy link
Contributor

@Johennes Johennes commented Sep 11, 2024

Fixes: #1943

Pull Request Checklist

Preview: https://pr1945--matrix-spec-previews.netlify.app

Fixes: matrix-org#1943
Signed-off-by: Johannes Marbach <n0-0ne+github@mailbox.org>
@Johennes Johennes changed the title Additional capabilities keys don't have to be objects Additional keys in GET /capabilities don't have to be objects. Sep 11, 2024
@Johennes Johennes changed the title Additional keys in GET /capabilities don't have to be objects. Additional keys in GET /capabilities don't have to be objects. Sep 11, 2024
@Johennes Johennes changed the title Additional keys in GET /capabilities don't have to be objects. Additional keys in GET /capabilities don't have to be objects Sep 11, 2024
@Johennes Johennes marked this pull request as ready for review September 11, 2024 11:21
@Johennes Johennes requested a review from a team as a code owner September 11, 2024 11:21
@KitsuneRal KitsuneRal merged commit 75e77b9 into matrix-org:main Sep 11, 2024
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

GET /capabilities shouldn't restrict additional properties to object types
2 participants