Haxe

Hmm you might have some issues with components re-rendering too much because you reassign an enum value that matches previous value but is a different reference and so is considered different (you can handle this in shouldComponentUpdate if needed)

Ah. I get the reference thing, but "they should be serializable", does that apply to anything else than loading/saving persistent data?

Haxe had some trouble with json serialisation of enums a long time ago iirc
I also think massive were (are still) using an older haxe version, so maybe this warning was about that
I don't think there're issues now, I'd say you can ignore the warning

What is the latest React version supported by haxe-react? (I'm right now looking for the possibility to use Fragments...)

Fragments are supported (`<>...</>` or `<Fragment key="somekey">...</Fragment>` when you need key, with `react.Fragment`)

Might miss some APIs but latest (or the one before the new jsx if it's not retrocompatible but I think it is) should be ok

Thanks, <@456226577798135808>! I missed that there was a compiler flag needed in react.Fragments to assure you're on R16.2+...

Taking some React-Native baby steps here... When running a Haxe-compiled app, I get the following: "Component Exception - Element type is invalid: expected a string (for built-in components) or a class/function...

I'm on Andriod studio: 4.1.1, react-native-cli: 2.0.1, react-native: 0.56.0

Usually (on web), you get this error when using an extern with a wrong @:jsRequire

```haxe
package myapp;

import react.ReactComponent;
import react.ReactMacro.jsx;
import react.native.component.*;

@:expose('App')
class App extends react.ReactComponent {

    public static function main() {
        new App();
    }

    override function render() {
        return jsx('
            <View>
                <Text>Hello</Text>
            </View>
        ');
    }
}
```

(Can't run that on the web, can I? Is there a RN-web-emulator..?)

Hm, it seem related to how haxe scopes and exports the App instance...

Could be. I think there are some haxe + react-native templates / test projects on github

If I use `-D js-es=6` and replace `$hx_exports["App"] = App;` with `export default App;`, it works.

For example https://github.com/haxe-react/haxe-react-native-sample/blob/master/src/Main.hx
Don't know why the registering is commented out x)

Try `@:native('App')` on `class App` maybe?

Thank you, klabs - I've tried them all... 🙂

Maybe it's a latest-version-of-RN-cli-thing.

Maybe, they all seem a little outdated :x

I'm using Thomas Fétivau's repo https://github.com/zabojad/haxe-react-native-stack now - seems to be a good match between react-native-cli and Haxe workflows...