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

Spec implicit filter event limit #1463

Merged
merged 3 commits into from
Mar 14, 2023

Conversation

Cadair
Copy link
Contributor

@Cadair Cadair commented Mar 14, 2023

This is an attempt to address #200

I think I am understanding the issue correctly. I took the default out of synapse I haven't looked in any other implementations to see if they also use the default of 10.

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

Signed-off-by: Stuart Mumford <[email protected]>
@Cadair Cadair requested a review from a team as a code owner March 14, 2023 12:05
Copy link
Member

@richvdh richvdh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Cadair thanks for picking this up!

@@ -14,7 +14,7 @@
title: EventFilter
properties:
limit:
description: The maximum number of events to return.
description: The maximum number of events to return. If not specified defaults to 10.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not entirely sure we should mandate this, or that we can mandate it, without going through the MSC process: it may well be that non-synapse implementations use a different default.

I think what we need to say instead is that if it's not specified, servers should use an implementation-specific default.

The limit param on GET /threads has sensible wording here.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, that makes more sense, I wasn't sure I had understood the original issue.

@richvdh
Copy link
Member

richvdh commented Mar 14, 2023

Also: please could you take a look at https://github.com/matrix-org/matrix-spec/blob/main/CONTRIBUTING.rst, particularly with respect to the need for a changelog file?

Cadair added 2 commits March 14, 2023 19:32
Signed-off-by: Stuart Mumford <[email protected]>
@Cadair Cadair force-pushed the spec_implicit_sync_limit branch from ee32fd2 to acba8e9 Compare March 14, 2023 19:36
@Cadair Cadair requested a review from richvdh March 14, 2023 19:38
Copy link
Member

@richvdh richvdh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great, thank you!

@richvdh richvdh merged commit 09e2250 into matrix-org:main Mar 14, 2023
@Cadair Cadair deleted the spec_implicit_sync_limit branch March 14, 2023 20:59
clokep pushed a commit to clokep/matrix-spec that referenced this pull request May 3, 2023
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.

2 participants