jitsi_app_c0

7362 提交

2 分支

目录树: 75c836c70c

提交图

作者	SHA1	备注	提交日期
Leonard Kim	9215b1e8b2	ref(app): move initialization into componentDidMount componentWillMount is a deprecated lifecycle method; componentDidMount should be used to kick off things like ajax. In the case of the _App hierarchy, a promise chain is used to perform initialization, and it is first started in the constructor by initializing storage. However, by the time storage is initialized, resolving the first promise, _App has already mounted. So, move it all to the componentDidMount lifecycle.	7 年前
Lyubo Marinov	8ff3ae0ab2	[Android] Introduce IncomingCallView (continued)	7 年前
Saúl Ibarra Corretgé	ea22d12581	[Android] Introduce IncomingCallView It's a separate view (on the native side) and app (on the JavaScript side) so applications can use it independently. Co-authored-by: Shuai Li <sli@atlassian.com> Co-authored-by: Pawel Domas <pawel.domas@jitsi.org>	7 年前

作者

SHA1

备注

提交日期

Leonard Kim

9215b1e8b2

ref(app): move initialization into componentDidMount

componentWillMount is a deprecated lifecycle method;
componentDidMount should be used to kick off things
like ajax. In the case of the _App hierarchy, a promise
chain is used to perform initialization, and it is
first started in the constructor by initializing
storage. However, by the time storage is initialized,
resolving the first promise, _App has already mounted.
So, move it all to the componentDidMount lifecycle.

7 年前

Lyubo Marinov

8ff3ae0ab2

[Android] Introduce IncomingCallView (continued)

7 年前

Saúl Ibarra Corretgé

ea22d12581

[Android] Introduce IncomingCallView

It's a separate view (on the native side) and app (on the JavaScript side) so
applications can use it independently.

Co-authored-by: Shuai Li <sli@atlassian.com>
Co-authored-by: Pawel Domas <pawel.domas@jitsi.org>

7 年前

3 次代码提交 (75c836c70c8f159816a6fb4a54b82b49c8937247)