-
Notifications
You must be signed in to change notification settings - Fork 385
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
Add top level filters for filtering by room id. #246
Conversation
room: | ||
properties: | ||
not_rooms: | ||
description: A list of room IDs to exclude. If this list is absent then no rooms | ||
are excluded. A matching room will be excluded even if it is listed in the 'rooms' |
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.
Backticks on 'rooms'
please.
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.
Fixed 9b4a37f
We're doing this for the purpose of guest access. We should probably mention that these filters will determine the rooms, or were you planning on doing that in another PR? It feels a little ming to be putting the global filter definition at the same level as the |
Add top level filters for filtering by room id Documented by matrix-org/matrix-spec-proposals#246
I was going to leave it to another PR to explain how they were used in guest access. |
Okay. Thoughts about shoving this to a |
I thought using the hierarchical position of the filters to indicate which parts of the response they applied to made it clearer than adding a |
Okay, that seems like a good enough reason to keep them where they are. If it turns out it's a mistake, we can always change it :) LGTM |
Add top level filters for filtering by room id.
Based on #245.