-
Notifications
You must be signed in to change notification settings - Fork 386
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
MSC3089: File tree structures #3089
base: old_master
Are you sure you want to change the base?
Conversation
This comment has been minimized.
This comment has been minimized.
"type": "m.branch", | ||
"state_key": "$event", | ||
"content": { | ||
"active": true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
note for mostly myself: we include a file name here to make simple edits easier.
edit: as name: string
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
also locked: true
for file locking
MSC: matrix-org/matrix-spec-proposals#3089 Includes part of MSC3088 (room subtyping): matrix-org/matrix-spec-proposals#3088 The NamespacedValue stuff is borrowed from the Extensible Events implementation PR in the react-sdk as a useful thing to put here. When/if the MSCs become stable, we'd convert the values to enums and drop the constants (or keep them for migration purposes, but switch to stable). This flags the whole thing as unstable because it's highly subject to change.
*Author's note: This proposal assumes the reader is familiar with the terminology of the reading | ||
materials mentioned above.* | ||
|
||
We introduce a new room subtype, `m.data_tree`, to be applied to spaces to denote that they are |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When you say "room subtype" here, should I assume MSC3088 m.room.purpose
state events with a state key of m.data_tree
? (There's enough MSCs that mention types floating around that I'm having trouble distinguishing them all...)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, sorry. Will leave this open as a reminder to clarify.
Rendered
Partial implementation: matrix-org/matrix-js-sdk#1732