This repository has been archived by the owner on Sep 11, 2024. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 828
Add ringing for matrixRTC #11870
Merged
Merged
Add ringing for matrixRTC #11870
Changes from 9 commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
be80e21
Add ringing for matrixRTC
toger5 ad26d1d
use typed CallNotifyContent
toger5 71263ea
update tests
toger5 dee9d79
change to callId
toger5 4148d6d
fix tests
toger5 353adc9
only ring in 1:1 calls
toger5 db6993e
call_id fallback
toger5 4359297
Update src/Notifier.ts
toger5 59600d0
review
toger5 a8ba346
add tests
toger5 ca824a4
more tests
toger5 ba62fc5
unused import
toger5 478da26
String -> string
toger5 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Non-blocking, but this really feels like logic that should live in the JS-SDK somehow
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The CallNotifyContent is declared in the js-sdk.
But I guess:
send_call_notify_event(notify_type: "ring" : "notify", mentions: IMentions, application: string, callId: string)
is what you are proposing? I was considering this but I almost prefer this kind of signature for this amount if fields:send(props: SendData)
vssend(prop1: data1, prop2:data2, ...)
The only thing we could get implicitly is
EventType.CallNotify
. The rest should be configurable anyways.