jitsi_mod

Struktur: 4e276471e5

Autor	SHA1	Nachricht	Datum
Lyubo Marinov	84b9c5f5fd	Coding style	vor 8 Jahren
Saúl Ibarra Corretgé	43c8fc6847	[RN] Fix mirroring video views on platforms with native support	vor 8 Jahren
Lyubomir Marinov	55a8b44224	Consistent middleware and reducer imports	vor 8 Jahren
Lyubomir Marinov	b50f858556	[flow] Expand the coverage of flow-monitored files	vor 8 Jahren
Lyubomir Marinov	5de1a74429	[flow] Take advantage of flow-typed	vor 8 Jahren
Lyubomir Marinov	349c04d8d1	Consistent naming of functions Until we make a decision on access modifier hints and adopt a respective coding style, consistency is king.	vor 8 Jahren
Lyubomir Marinov	eaed9db1e7	Name folders consistently	vor 8 Jahren
Lyubomir Marinov	4f8b7a934c	Comply w/ coding style	vor 8 Jahren
Lyubomir Marinov	5f21e4c5b6	Introduce Platform in React React Native provides Platform.	vor 8 Jahren
Saúl Ibarra Corretgé	e71e6c5b79	Name Redux actions consistently Redux actions which represent "commands" should be imperative, and those representing events should use the past tense.	vor 8 Jahren
Lyubomir Marinov	daf56455a5	Use Symbol for Redux action types to prevent conflicts	vor 8 Jahren
Lyubomir Marinov	0db33bb45c	React propTypes as static class properties	vor 8 Jahren
Ilya Daynatovich	c3428e8213	Split React components out of index.html	vor 8 Jahren
Lyubomir Marinov	4997ae79e3	Fix toolbar's mute buttons when starting muted The toolbar's mute buttons depict respective features/base/media states. However, (un)muting is practically carried out by features/base/tracks. When the mobile app enters a conference configured to invite the joining participant to mute themselves, the tracks would be muted but the toolbar's mute buttons would not reflect that.	vor 8 Jahren
Lyubomir Marinov	7f3ff13c18	Merge jitsi-meet-react's mobile support As a step toward merging jitsi-meet-react with jitsi-meet to share as much source code as possible between mobile and Web, merge the part of jitsi-meet-react's source tree which supports mobile inside the jitsi-meet source tree and leave jitsi-meet-react's Web support in the source code revision history but don't have it in master anymore because it's different from jitsi-meet's Web support. In other words, the two projects are mechanically merged at the file level and don't really share source code between mobile and Web.	vor 8 Jahren
Lyubomir Marinov	d55e0f70d9	Import jitsi/jitsi-meet-react#2f23d98 As an intermediate step on the path to merging jitsi-meet and jitsi-meet-react, import the whole source code of jitsi-meet-react as it stands at 2f23d98424 i.e. the lastest master at the time of this import. No modifications are applied to the imported source code in order to preserve a complete snapshot of it in the repository of jitsi-meet and, thus, facilitate comparison later on. Consequently, the source code of jitsi-meet and/or jitsi-meet-react may not work. For example, jitsi-meet's jshint may be unable to parse jitsi-meet-react's source code.	vor 8 Jahren

17 Commits (4e276471e574a22eb2bda95da16f35b51e9ce3d2)