I am testing the use of flow on Fiber and seems to be very promising, to know more information of him access here. What do you think of this?
[ ] isomorphic/FiberComponent
[ ] isomorphic/FiberCreateComponent
[ ] isomorphic/FiberElement
[X] isomorphic/FiberRender
[ ] isomorphic/FiberUpdateQueue
[ ] renderers/dom/FiberDOMEvents
[ ] renderers/dom/FiberDOMRender
To check flow errors, run yarn run flow.
Use of __DEV__
I added a configuration so that we can use the __DEV__ variable to display information in a block, such as error messages or warnings. Things we do not want in a production environment.
Example:
if (__DEV__) {
console.log('In development');
}
Blocks that use __DEV__ are removed when compiled for production.
Coverage remained the same at 94.444% when pulling bf9db2c4fc8d99cf6589ab2f658422fd566c7161 on matuzalemsteles:flow into ec2eb38c0c83ff3b94028961e32eabc9a8abe461 on liferay-labs-br:master.
Use of flow
I am testing the use of flow on Fiber and seems to be very promising, to know more information of him access here. What do you think of this?
isomorphic/FiberComponent
isomorphic/FiberCreateComponent
isomorphic/FiberElement
isomorphic/FiberRender
isomorphic/FiberUpdateQueue
renderers/dom/FiberDOMEvents
renderers/dom/FiberDOMRender
To check flow errors, run
yarn run flow
.Use of
__DEV__
I added a configuration so that we can use the
__DEV__
variable to display information in a block, such as error messages or warnings. Things we do not want in a production environment.Example:
Blocks that use
__DEV__
are removed when compiled for production.