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.

Sign up for GitHub

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

Jump to bottom

Clarify that null is not allowed for most properties #472

Open
turt2live opened this issue May 23, 2019 · 2 comments
Open

Clarify that null is not allowed for most properties #472

turt2live opened this issue May 23, 2019 · 2 comments
Labels
A-Client-Server Issues affecting the CS API clarification An area where the expected behaviour is understood, but the spec could do with being more explicit

Comments

@turt2live
Copy link
Member

No description provided.

@turt2live turt2live added clarification An area where the expected behaviour is understood, but the spec could do with being more explicit A-Client-Server Issues affecting the CS API labels May 23, 2019
@turt2live turt2live self-assigned this May 23, 2019
@turt2live turt2live mentioned this issue May 23, 2019
Closed
3 tasks
@turt2live turt2live removed their assignment May 29, 2019
@ShadowJonathan
Copy link
Contributor

ShadowJonathan commented Sep 22, 2020 •
edited
Loading

Is placing null for an omitted key specifically not allowed for any and all non-"required" keys, or for just a few (with those exceptions noted down)?

@turt2live turt2live mentioned this issue Jan 12, 2021
Closed
@richvdh
Copy link
Member

richvdh commented Jul 28, 2021

Generally, implementations receiving a property in a request/response body will expect that property to be valid. So, in general, if an optional property is to be omitted, you should omit it, rather than set it to null.

@jplatte jplatte mentioned this issue Aug 22, 2021
Closed
@turt2live turt2live mentioned this issue May 26, 2019
Open
@richvdh richvdh transferred this issue from matrix-org/matrix-spec-proposals Mar 1, 2022
@richvdh richvdh mentioned this issue Nov 15, 2022
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-Client-Server Issues affecting the CS API clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@turt2live @richvdh @ShadowJonathan