Daniel Calviño Sánchez 0dcdd6161f Move nick handling out of PeerConnectionWrapper ... PeerConnectionWrappers should not be concerned with the nick of participants. Moreover, the nick is included in offers and answers due to legacy reasons and only when the internal signaling server is used. Due to that the nick was moved out of PeerConnectionWrapper; although the handling is now different the end result should be the same (there might be some differences in very specific sequences of events, but in any case all this is just a temporary step and any leftover issue should be addressed once call participants and peer connections are split). As the PeerConnectionWrapper does not keep track of the nick now the nick changed event is always emitted when a nick changed data channel message is received, even if the nick did not actually change. Nevertheless, before it was anyway always emitted if it was for a user and only when it was for a guest it was emitted only on real changes. In any case this is not expected to cause any issue (other than some unneeded view updates, but that will be addressed at a later point by updating the views only when the model actually changed). Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>		2022-12-28 11:47:55 +01:00
..
schemas/com.nextcloud.talk.data.source.local.TalkDatabase
src	Move nick handling out of PeerConnectionWrapper	2022-12-28 11:47:55 +01:00
build.gradle	Weekly 15.2.0 Alpha 03	2022-12-26 03:12:55 +00:00
lint.xml
proguard-rules.pro