jiti-meet/react/features/conference/components/index.js

// @flow

export { default as Conference } from './Conference';
noticeMessage is not shown (refs #3295) * Get back the Notice class * Add Notice component in the Conference web view * Notice is not exported in index.js. Only used internally by Conference. * noticeMessage value obtained from features/base/config * using mapStateToProps * value is stored in the internal _message property * Notice component, orignal in `toolbox` is moved from `toolbox/components` to `conference/components` * Notice component only implemented and renderable in web views * Dummy `conference/components/Notice.naive.js` This patch is partially based in the removed logic included originally in: commit 59a74153dc9ec0432cbc6f1fac5ef9c1b3566cd4 (tag: jitsi-meet_1886, tag: jitsi-meet_1885, tag: 1797, tag: 1796) Author: Ilya Daynatovich <shupuercha@gmail.com> Date: Mon Mar 20 11:04:54 2017 -0500 Toolbar notice as React Component In reply to: Saúl Ibarra Corretgé @saghul> comments Signed-off-by: Pablo Saavedra <psaavedra@igalia.com> 2018-07-24 13:08:26 +00:00			`// @flow`

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 https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 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. 2016-10-05 14:36:59 +00:00			`export { default as Conference } from './Conference';`