![]() ![]() What is going on here? I would like to use the Fragment shorthand syntax, and this issue is stopping me from doing that for now. With an explicit import of Fragment, however, flow does not complain. private/tmp/flow/flowlib_2349df3a/react.jsĢ55│ +initializeTouchEvents: typeof initializeTouchEvents,Ģ56│ +checkPropTypes: typeof checkPropTypes,Ģ58│ +createElement: typeof createElement,Ģ60│ +createFactory: typeof createFactory,Ģ61│ +isValidElement: typeof isValidElement,Ģ63│ +PureComponent: typeof PureComponent, Using react Fragments with either or the shorthand syntax like so import React from 'react'įlow complains with the following error (it's an indentical error for both, just showing output for ComponentA here) Cannot get React.Fragment because property Fragment is missing in object type. Thanks to Gajus Kuizinas and other contributors who prototyped the Fragment component in open source.I am using react v16.3.0 and flow-bin v0.69.0 Special thanks to the TypeScript and Flow teams, as well as the Babel maintainers, who helped make tooling support for the new syntax go seamlessly. A big thanks to everyone who filed issues, contributed to syntax discussions, reviewed pull requests, added support for JSX fragments in third party libraries, and more! This release was made possible by our open source contributors. Many tests were rewritten against the public API.Expose react-reconciler/reflection with utilities useful to custom renderers. ![]() Fix setState() callback firing too early when called from componentWillMount.Fix radio buttons not receiving the onChange event in some cases.Fix radio buttons not getting checked when using multiple lists of radios.Support experimental Call/Return types in React.Children utilities. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |