Skip to content

Conversation

@NegativeMjark
Copy link
Contributor

No description provided.

Copy link
Contributor

Choose a reason for hiding this comment

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

Should the JSON be URL-encoded? Or something else?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It should be passed like any other query parameter, encoded as UTF-8 and URL encoded.

Copy link
Contributor

Choose a reason for hiding this comment

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

We do very explicitly state that all strings must be UTF-8 encoded in the API Standards section. As far as I know, this is the first place where a query parameter is anything other than a string or an int.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Is saying that it is passed a string sufficient? c3a1318

@illicitonion
Copy link
Contributor

LGTM

NegativeMjark added a commit that referenced this pull request Dec 9, 2015
Allow the filter JSON to be passed inline in the /sync request
@NegativeMjark NegativeMjark merged commit a33e49f into master Dec 9, 2015
NegativeMjark added a commit to matrix-org/synapse that referenced this pull request Dec 9, 2015
NegativeMjark added a commit to matrix-org/synapse that referenced this pull request Dec 9, 2015
Allow filter JSON object in the filter query parameter in /sync

Documented by matrix-org/matrix-spec-proposals#224
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.

3 participants