8 Commits

Author	SHA1	Message	Date
Robin	2ac6cdeb46	Improve internal model of ringing, expose ringing intent to call UI ... I found our code's internal model of ringing a little overgrown (it had superfluous states like 'unknown') and difficult to extend with metadata or callbacks relating to ring attempts. By modeling ringing instead as a stream of ring attempts, where each attempt has an intent, a recipient, and an eventual outcome (accept/decline/timeout), I find it more natural to work with. This makes room for a future 'try again' callback to allow ringing someone again after a timeout, and also forced me to look for a simpler solution to the duplicate leave sound effects. I exposed the intent of the ringing attempt to the call UI so I can later use it in the header.	2026-06-11 12:12:27 +02:00
Valere	a0ad238952	fix: DidSendCallNotification is not emitting array anymore	2026-02-03 15:29:19 +01:00
Timo K	c1b2346e22	Update tests based on new js-sdk changes ... (no more legacy notify event)	2026-01-27 16:49:25 +01:00
Valere	614762b5f8	fixup headers	2025-11-18 10:13:10 +01:00
Timo K	b9ad83bf3b	fix a couple of more tests.	2025-11-14 18:45:07 +01:00
Valere	6d8d2d2384	refact: extract withCallViewModel in test utils file	2025-11-14 17:30:02 +01:00
Timo K	b731c2e9fd	dont import withCallViewModel in Lifecycle test	2025-11-14 16:53:43 +01:00
Timo K	f6d0d7323e	fix call lifecycle and add tests.	2025-11-14 16:01:43 +01:00