52c77cb4b4
* Implement core redaction logic - Add a new `redactions_table.go` which tracks the mapping of the redaction event ID and the redacted event ID - Mark redactions as 'validated' when we have both events. - When redactions are validated, add `unsigned.redacted_because` and modify the `eventJSON` accordingly. Note: We currently do NOT redact the event content - it's gated behind a feature flag - until we have tested redactions a bit more. * Linting |
||
---|---|---|
.. | ||
event_json_table.go | ||
event_state_keys_table.go | ||
event_types_table.go | ||
events_table.go | ||
invite_table.go | ||
membership_table.go | ||
previous_events_table.go | ||
published_table.go | ||
redactions_table.go | ||
room_aliases_table.go | ||
rooms_table.go | ||
state_block_table_test.go | ||
state_block_table.go | ||
state_snapshot_table.go | ||
storage.go | ||
transactions_table.go |