-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Improve documentation for EventContext fields #6319
Conversation
96f4455
to
b70e641
Compare
b70e641
to
069098d
Compare
For a *rejected* state event, where the state of the rejected event is | ||
ignored, this state_group should never make it into the | ||
event_to_state_groups table. Indeed, inspecting this value for a rejected | ||
state event is almost certainly incorrect. |
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.
(I wonder if we should make accessing state_group
raise if its rejected)
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.
yup could do!
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.
well who knew, this identified a bug. I'm going to pull this out to a separate PR.
For an outlier, where we don't have the state at the event, this will be | ||
None. | ||
|
||
prev_group: If it is known, ``state_group``'s prev_group. Note that this being |
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.
Might be worth noting that this is not the state group associated with prev_state_ids
Per review comments: add some sanity checks on accessing state_group etc for rejected events.
This reverts commit f84119b. This turned out to identify some bugs, so I'm going to pull the whole lot out to a separate PR.
* commit '408600282': Improve documentation for EventContext fields (#6319)
No description provided.