-
-
-
These are treated differently from the other notifications tied to accounts, as those are transient and ...
-
I think you can't just
continue
, as if you have something like:- notification 1 (
account1
, not connection error) - notification 2 (
account2
, connection error) - notification 3 (
account1
, not connection error)
and you are deleting
account1
, then the continue will not trigger ahave_same
change for notification 2, and it will believe it should remove all notifications. - notification 1 (
-
Fix connection errors getting deleted when an account is disconnected
Review Request #1944 — Created Oct. 23, 2022 and submitted
Fix connection errors getting deleted when an account is disconnected
- Ran the unit tests with the new test
- Caused a resource conflict on XMPP to verify that notification was displayed
- Attempted to connect an IRC account that had a bad hostname and verified that notification was displayed.
- Not integration testing was done for Finch.
Summary | ID |
---|---|
cd2f5442b93e82c1ddf1bb59127b46b7f5cd6cfb |
Description | From | Last Updated |
---|---|---|
notifications |
|
|
These are treated differently from the other notifications tied to accounts, as those are transient and ... |
|
|
I think you can't just continue, as if you have something like: notification 1 (account1, not connection error) notification 2 … |
|
|
notifications |
|
|
fourth |
|
|
position zero. |
|
|
s/call empty/empty/ s/it's/its/ |
|
|
4, or maybe leave out the number. |
|
- Change Summary:
-
Address issues, fix the handling of connection errors, and remove the attempts to linking to an enum member as that is not supported by gi-docgen.
- Commits:
-
Summary ID 6eec14d6c45cb9251ffaa79899b27edd04be3677 d2675700b6c6f914f13c19a8b86aa5ead7fb9001