Unfloyded/Legamunt
0
0
Fork 0
Code Activity

Do not filter the status collection after muting and blocking (#5815)

Browse source 
Filtering the status collection wipes out even the profiles of muted and
blocked accounts. However, the behavior is inconsistent with the server-
side behavior.
This commit is contained in:
Akihiko Odaki 2017-11-26 09:45:17 +09:00 • committed by Eugen Rochko
parent 57fe4102ea
commit fd87e5a53b
2 changed files with 13 additions and 19 deletions
Download patch file Download diff file Expand all files Collapse all files

19
app/javascript/mastodon/reducers/statuses.js
View file

@ -22,10 +22,6 @@ import {
TIMELINE_DELETE,
TIMELINE_EXPAND_SUCCESS,
} from '../actions/timelines';
import {
ACCOUNT_BLOCK_SUCCESS,
ACCOUNT_MUTE_SUCCESS,
} from '../actions/accounts';
import {
NOTIFICATIONS_UPDATE,
NOTIFICATIONS_REFRESH_SUCCESS,
@ -88,18 +84,6 @@ const deleteStatus = (state, id, references) => {
return state.delete(id);
};
const filterStatuses = (state, relationship) => {
state.forEach(status => {
if (status.get('account') !== relationship.id) {
return;
}
state = deleteStatus(state, status.get('id'), state.filter(item => item.get('reblog') === status.get('id')));
});
return state;
};
const initialState = ImmutableMap();
export default function statuses(state = initialState, action) {
@ -139,9 +123,6 @@ export default function statuses(state = initialState, action) {
return normalizeStatuses(state, action.statuses);
case TIMELINE_DELETE:
return deleteStatus(state, action.id, action.references);
case ACCOUNT_BLOCK_SUCCESS:
case ACCOUNT_MUTE_SUCCESS:
return filterStatuses(state, action.relationship);
default:
return state;
}