Mateusz Żebrak authored 1 year ago and Jakub Ziebinski committed 1 year ago

Previously it was required for the callback do accept one and only one
param.

Mateusz Żebrak authored 1 year ago and Jakub Ziebinski committed 1 year ago

This caused some issues with providers when
fast broadast was used on the operatin summary screen
and self.provider.content was referenced.
That's because of screen resume was posted during each pop_screen
and looks like provider catched that ScreenResume after screen yielding
that provider was acutally popped (so NoMatches occured when querying
provider which notified about change).

See Integrations section of 23.9.0 changeolog: https://black.readthedocs.io/en/stable/change_log.html#id42

Store transaction history in Clive app instance, in TUI tests rework method for getting transaction id from notification

Created common method: extract_message_from_notification
that can be used for looking for other things than notification id.

Such a method will also check for the expected message in
notification history.