status-desktop/ui
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
..
StatusQ fix: Use `StatusCursorDelegate` for password inputs (#10890) 2023-06-01 21:23:22 +03:00
app fix(contacts): fix inconsistency when banning or unbanning contact 2023-06-01 14:25:20 -04:00
fonts fix(cpp): make libraries which are not dynamically loaded static 2022-08-02 15:30:08 +02:00
i18n chore(translations): update translations 2023-03-06 21:35:32 +01:00
imports fix: Use `StatusCursorDelegate` for password inputs (#10890) 2023-06-01 21:23:22 +03:00
include/StatusDesktop/Monitoring chore(general): move cpp files of monitoring tool from DOtherSide to ui dir 2023-02-09 14:27:53 +01:00
src/StatusDesktop/Monitoring chore(general): move cpp files of monitoring tool from DOtherSide to ui dir 2023-02-09 14:27:53 +01:00
MonitoringSources.cmake chore(general): move cpp files of monitoring tool from DOtherSide to ui dir 2023-02-09 14:27:53 +01:00
generate-rcc.go fix(StatusQ): StatusQ is QML module (#10207) 2023-04-14 11:18:56 +03:00
main.qml test(suite_onboarding): fix tests (#10260) 2023-05-04 18:18:19 +02:00
nim-status-client.pro feat(general): Initial setup for app monitoring tool 2023-01-13 13:47:08 +01:00