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.

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

Organise non-state event schemas in a separate section or index type to corresponding section #3369

Closed
ShadowJonathan opened this issue Aug 29, 2021 · 1 comment
Labels
aesthetic A suggestion or issue relating to the representation of the spec

Comments

@ShadowJonathan
Copy link
Contributor

MSC #3368 triggered me thinking about this, there's a lot of message event schemas scattered all over the spec in different areas, while i think it'd help if either;

  • an index for it existed (m.room.message -> link)
  • a full section is dedicated to all message schemas alone, and the rest of the spec links to it instead.

This is mainly to make the spec more friendly to traverse, and to easily list all "official" event formats side-by-side.

This is specifically for non-state events at the moment, I think state events are still important in their context, but maybe a simple index would be helpful for that as well.

@ShadowJonathan ShadowJonathan added the aesthetic A suggestion or issue relating to the representation of the spec label Aug 29, 2021
@ShadowJonathan ShadowJonathan changed the title Organise non-state event schemas in a separate section Organise non-state event schemas in a separate section or index type to corresponding section Aug 29, 2021
@richvdh
Copy link
Member

richvdh commented Sep 20, 2021

I think this is a subset of https://github.com/matrix-org/matrix-doc/issues/3404.

@richvdh richvdh closed this as completed Sep 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
aesthetic A suggestion or issue relating to the representation of the spec
Projects
None yet
Development

No branches or pull requests

2 participants