status-desktop/ui/app/AppLayouts/Chat
Jonathan Rainville ceb810e63d fix(contacts): fix inconsistency when banning or unbanning contact
Fixes #10501

The problem was that didn't have access to the updated contact from status-go after banning or unbanning, so we just changed the banned property, but there is more that gets changed in the backend, like `removed` being set to `true` as well.
With this fix, when you unban someone, you go back to a fresh start, as **non** contact, so you need to send a request again. That was the state you got if you restarted the app, so "re-sync" the state with status-go.
Another issue was on the frontend (QML). When banned,  and after restarting to get the right state, the unban button would be disabled and the Add contact request button would show, which is not good. We only want to send requests when unbanned.
2023-06-01 14:25:20 -04:00
..
controls fix(StatusScrollView): Change implementation to inherit ScrollView (#10789) 2023-05-31 23:58:23 +03:00
helpers feat(HoldingsDropdown): airdrops tokens support added 2023-05-08 11:44:10 +02:00
layouts tst(tst_communityMintTokens): Mint Tokens welcome screen 2023-05-18 16:04:39 +03:00
panels fix(StatusScrollView): Change implementation to inherit ScrollView (#10789) 2023-05-31 23:58:23 +03:00
popups fix(StatusScrollView): Change implementation to inherit ScrollView (#10789) 2023-05-31 23:58:23 +03:00
stores fix(contacts): fix inconsistency when banning or unbanning contact 2023-06-01 14:25:20 -04:00
views fix(contacts): fix inconsistency when banning or unbanning contact 2023-06-01 14:25:20 -04:00
ChatLayout.qml fix(newChat): fix sending messages in new ad hoc chat with new store 2023-05-05 09:36:14 -04:00
qmldir feat(onboarding): Added SplashScreen 2022-03-08 14:02:24 -05:00