react-closure-compiler
react-closure-compiler copied to clipboard
Tooling to teach Closure Compiler about React
Very cool project! I gave it a shot and integrated it into our build process, but I'm running into an exception. I'm completely unfamiliar with the Closure Compiler codebase, so...
A component method of the form: ```js /** * @param {SomeType} type * @return {SomeType} */ someMethod({ destructuredField1, destructuredField2, }) { ... return 1; }, ``` Produces a warning: ```...
Add an (optional) transformation similar to https://babeljs.io/docs/plugins/transform-react-inline-elements/ ([source](https://github.com/babel/babel/tree/master/packages/babel-plugin-transform-react-inline-elements)).
Add an (optional) transformation similar to https://babeljs.io/docs/plugins/transform-react-constant-elements/ ([source](https://github.com/babel/babel/tree/master/packages/babel-plugin-transform-react-constant-elements)).
Check both `propTypes` as well as props passed to `React.createElement`
Upon first glance ReactCompilerPass looks similar to PolymerPass. I wonder how hard it would be to contribute this back to Closure Compiler?
`JsDocInfoBuilder`'s `build()` signature has changed, among other API changes.
Got error trying to run demo. Ubuntu 15.04 java version "1.7.0_79" OpenJDK Runtime Environment (IcedTea 2.5.6) (7u79-2.5.6-0ubuntu1.15.04.1) OpenJDK 64-Bit Server VM (build 24.79-b02, mixed mode) Apache Ant(TM) version 1.9.4 compiled...
Since we actually have tests
Right now there's no need for `@override` annotations on `shouldComponentUpdate` and the like, since JSDoc/parameter types from the component methods are copied automatically. However, if the annotation is present, we...