haxe-react

haxe-react copied to clipboard

`ReactMacro.jsx()` can not process this code: ```haxe class CompRenderFunctionProps extends ReactComponentOfPropsReactElement}> {} function fn() return jsx(''); ReactMacro.jsx(''); ```

terurou

SyntheticEvent

3

kevinresol

very excited about this project

1

I have always wanted to use haxe but the hurdles are a bit much to be productive in haxe while using react, especially the string based JSX, does this project...

hyusetiawan

This should not compile, or at least not without a warning: ```jsx Children passed as subtree ``` (currently, subtree takes priority)

kLabz

js-object not needed anymore?

2

Am I wrong or is js-object not needed anymore since Haxe 4?

zabojad

see https://github.com/benmerckx/genes/issues/13#issuecomment-597417802 I think having a `var __tre(get, never)` plus an `inline` getter should preserve the performance, while making it genes-friendly

kevinresol

React will give the following runtime error: ``` Warning: Unsafe legacy lifecycles will not be called for components using new component APIs. MyComponent uses getDerivedStateFromProps() but also contains the following...

kLabz

Inconsistent defaultProps behavior in debug / no debug mode

2

Hi, Rudy! It looks like react-next has this bug too. https://github.com/massiveinteractive/haxe-react/issues/131

djaonourside

`ReactType` currently fallback to `div` when there's an issue with resolving an extern component.

kLabz

With compilation server on, and when using modular (maybe even without modular?), the macro setting `displayName` on jsxStatic components can break at runtime (maybe when some component move from a...

kLabz