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

spec is unclear about how to handle strings when a number is expected #615

Open
uhoreg opened this issue May 1, 2020 · 2 comments
Open

spec is unclear about how to handle strings when a number is expected #615

uhoreg opened this issue May 1, 2020 · 2 comments
Labels
clarification An area where the expected behaviour is understood, but the spec could do with being more explicit meta Something that is not a spec change/request and is not related to the build tools

Comments

@uhoreg
Copy link
Member

uhoreg commented May 1, 2020

synapse seems to parse strings in PL events, which is unexpected, IMHO
@turt2live turt2live added clarification An area where the expected behaviour is understood, but the spec could do with being more explicit meta Something that is not a spec change/request and is not related to the build tools labels May 1, 2020
@richvdh
Copy link
Member

richvdh commented May 1, 2020

I think this is a subset of #365

@KitsuneRal
Copy link
Member

We've already had a mess with strings vs. floats in tag orders before; agree that parsing numbers from strings should not be expected.

@richvdh richvdh transferred this issue from matrix-org/matrix-spec-proposals Mar 1, 2022
@Johennes Johennes mentioned this issue Jun 12, 2024
Closed
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 expected behaviour is understood, but the spec could do with being more explicit meta Something that is not a spec change/request and is not related to the build tools
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@uhoreg @turt2live @richvdh @KitsuneRal