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 empty strings === null === undefined unless otherwise stated #2007

Closed
turt2live opened this issue May 21, 2019 · 4 comments
Closed

Clarify that empty strings === null === undefined unless otherwise stated #2007

turt2live opened this issue May 21, 2019 · 4 comments
Labels
clarification An area where the spec could do with being more explicit client-server Client-Server API

Comments

@turt2live
Copy link
Member

No description provided.

@turt2live
Copy link
Member Author

eg: https://github.com/matrix-org/matrix-doc/issues/2006

@turt2live turt2live added clarification An area where the spec could do with being more explicit client-server Client-Server API labels May 21, 2019
@erikjohnston
Copy link
Member

Really? Where do we do this?

@richvdh
Copy link
Member

richvdh commented May 23, 2019

Personally I thought that the general rules were:

  • you weren't alllowed to pass null over the API unless it was explicitly mentioned
  • you signal the absence of a value by not sending it
  • empty string is a specific value which is different from null or <absent>

@turt2live
Copy link
Member Author

We indeed are saying null isn't allowed for the general case

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
clarification An area where the spec could do with being more explicit client-server Client-Server API
Projects
None yet
Milestone
No milestone
Development

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