bigbuffet/bigbuffet-rw
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Notifications: actually, do still use the legacy StatusContainer as it does a selector we need

Browse source
This commit is contained in:
Alex Gleason 2022-08-13 10:40:56 -05:00
parent a0e79bfe10
commit 7b75faf74c
No known key found for this signature in database
GPG key ID: 7211D1F99744FBB7
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
app/soapbox/features/notifications/components/notification.tsx
View file

@ -10,9 +10,9 @@ import { getSettings } from 'soapbox/actions/settings';
import { hideStatus, revealStatus } from 'soapbox/actions/statuses';
import Icon from 'soapbox/components/icon';
import Permalink from 'soapbox/components/permalink';
import Status from 'soapbox/components/status';
import { HStack, Text, Emoji } from 'soapbox/components/ui';
import AccountContainer from 'soapbox/containers/account_container';
import StatusContainer from 'soapbox/containers/status_container';
import { useAppDispatch, useAppSelector } from 'soapbox/hooks';
import { makeGetNotification } from 'soapbox/selectors';
import { NotificationType, validType } from 'soapbox/utils/notification';
@ -303,8 +303,8 @@ const Notification: React.FC<INotificaton> = (props) => {
case 'update':
case 'pleroma:emoji_reaction':
return status && typeof status === 'object' ? (
<Status
status={status}
<StatusContainer
id={status.id}
withDismiss
hidden={hidden}
onMoveDown={handleMoveDown}