diff options
author | Brendan Abolivier <babolivier@matrix.org> | 2019-12-16 12:14:12 +0000 |
---|---|---|
committer | Brendan Abolivier <babolivier@matrix.org> | 2019-12-16 12:14:12 +0000 |
commit | 487f1bb49d5eb5840c7dd70d95ac53f2b24eba21 (patch) | |
tree | 17cc102db01d865ad65afec6eb42cea89073d6c2 /synapse/visibility.py | |
parent | More rewording of changelog. (diff) | |
download | synapse-487f1bb49d5eb5840c7dd70d95ac53f2b24eba21.tar.xz |
Use the filtered version of an event when responding to /context requests for that event
Sometimes the filtering function can return a pruned version of an event (on top of either the event itself or an empty list), if it thinks the user should be able to see that there's an event there but not the content of that event. Therefore, the previous logic of 'if filtered is empty then we can use the event we retrieved from the database' is flawed, and we should use the event returned by the filtering function.
Diffstat (limited to 'synapse/visibility.py')
0 files changed, 0 insertions, 0 deletions