Fix the table of content for room versions (#1884)
* Fix ToC for room versions pages Like for the cs-module shortcode, use .RenderShortcodes instead of .Content for the rver-fragment shortcode, so the headings are detected by Hugo. Signed-off-by: Kévin Commaille <zecakeh@tedomum.fr> * Change the way "this version" is detected in added-in and changed-in shortcodes Now that we use .RenderShortcodes in the rver-fragment shortcode, we cannot remove the output of these shortcodes dynamically because they are replaced by a temporary placeholder due to Hugo's internals. Instead, since the `this` parameter was only used for room version, we always use the `v` parameter and compare with the version provided in the page's front matter. Signed-off-by: Kévin Commaille <zecakeh@tedomum.fr> * Add changelog Signed-off-by: Kévin Commaille <zecakeh@tedomum.fr> * Add version front matter for v11 Signed-off-by: Kévin Commaille <zecakeh@tedomum.fr> * Update changelogs/room_versions/newsfragments/1884.clarification --------- Signed-off-by: Kévin Commaille <zecakeh@tedomum.fr> Co-authored-by: Travis Ralston <travpc@gmail.com>
This commit is contained in:
parent
18628dc5d7
commit
3af77f0cb4
20 changed files with 60 additions and 51 deletions
|
@ -2,6 +2,7 @@
|
|||
title: Room Version 6
|
||||
type: docs
|
||||
weight: 60
|
||||
version: 6
|
||||
---
|
||||
|
||||
This room version builds on [version 5](/rooms/v5) while changing various
|
||||
|
@ -15,7 +16,7 @@ which implement the redaction algorithm locally should refer to the
|
|||
|
||||
### Redactions
|
||||
|
||||
{{< added-in this=true >}} All significant meaning for `m.room.aliases`
|
||||
{{< added-in v=6 >}} All significant meaning for `m.room.aliases`
|
||||
has been removed from the redaction algorithm. The remaining rules are
|
||||
the same as past room versions.
|
||||
|
||||
|
@ -40,11 +41,11 @@ in [room version 5](/rooms/v5).
|
|||
|
||||
### Authorization rules
|
||||
|
||||
{{< added-in this=true >}} Rule 4, which related specifically to events
|
||||
{{< added-in v=6 >}} Rule 4, which related specifically to events
|
||||
of type `m.room.aliases`, is removed. `m.room.aliases` events must still pass
|
||||
authorization checks relating to state events.
|
||||
|
||||
{{< added-in this=true >}} Additionally, the authorization rules for events of
|
||||
{{< added-in v=6 >}} Additionally, the authorization rules for events of
|
||||
type `m.room.power_levels` now include a `notifications` property under
|
||||
`content`. This updates rules 10.4 and 10.5 (now 9.4 and 9.5), which checked
|
||||
the `events` property.
|
||||
|
@ -174,12 +175,12 @@ The rules are as follows:
|
|||
power level, reject.
|
||||
2. If the new value is higher than the `sender`'s current power
|
||||
level, reject.
|
||||
4. {{< changed-in this="true" >}}
|
||||
4. {{< changed-in v=6 >}}
|
||||
For each entry being changed in, or removed from, the `events` or
|
||||
`notifications` properties:
|
||||
1. If the current value is greater than the `sender`'s current
|
||||
power level, reject.
|
||||
5. {{< changed-in this="true" >}}
|
||||
5. {{< changed-in v=6 >}}
|
||||
For each entry being added to, or changed in, the `events` or
|
||||
`notifications` properties:
|
||||
1. If the new value is greater than the `sender`'s current power
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue