Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

Why don't we validate the JSON that clients submit for core event types like m.room.join_rules (SYN-720) #1391

Open
matrixbot opened this issue Jul 3, 2016 · 0 comments
Labels
A-Validation 500 (mostly) errors due to lack of event/parameter validation T-Enhancement New features, changes in functionality, improvements in performance, or user-facing enhancements.

Comments

@matrixbot
Copy link
Member

Submitted by @​matthew:matrix.org
Especially in initial_state?

(Imported from https://matrix.org/jira/browse/SYN-720)

@matrixbot matrixbot changed the title Why don't we validate the JSON that clients submit for core event types like m.room.join_rules (SYN-720) Why don't we validate the JSON that clients submit for core event types like m.room.join_rules (https://github.com/matrix-org/synapse/issues/1391) Nov 7, 2016
@matrixbot matrixbot changed the title Why don't we validate the JSON that clients submit for core event types like m.room.join_rules (https://github.com/matrix-org/synapse/issues/1391) Why don't we validate the JSON that clients submit for core event types like m.room.join_rules (SYN-720) Nov 7, 2016
@reivilibre reivilibre added A-Validation 500 (mostly) errors due to lack of event/parameter validation T-Enhancement New features, changes in functionality, improvements in performance, or user-facing enhancements. labels May 19, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
A-Validation 500 (mostly) errors due to lack of event/parameter validation T-Enhancement New features, changes in functionality, improvements in performance, or user-facing enhancements.
Projects
None yet
Development

No branches or pull requests

2 participants