You can use conditional and support both, for a smooth transition

(if you have the energy)

I don't think you can since it doesn't parse

why not

meta.extract(if(Context.defined('haxe4') ":react.wrap" else ":wrap")

no?

In macros yeah, but there would be

#if react.xx

everywhere, and those wouldn't parse in haxe < 4

argh.... I misunderstood scoped metas

I was thinking

@:react.xx

ok yeah that seems to be a tough choice

But yeah I should move to scoped metas too

Well at least support them

I don't think I want to have

@:react.wrap

everywhere

I want them though, much clearer

In a react codebase it's mostly redundant

Maybe with coconut/tink which are meta heavy it's less clear, though

that's a confusing abbreviation, I thought you meant Vim's coc at first 😛

Whoops of course, not intentional x)

does haxe3 supports

haxe Main -D scoped.define=1

?

It defines scoped_define I think

I don't think it does?

It does for -, I'm checking with .

otherwise thx.core wouldn't have needed

-D thx_core

in its extraParams

Yeah, it doesn't

Do you guys know if this is still given any consideration https://github.com/HaxeFoundation/haxe-evolution/issues/60

What do you mean?

hey guys I'm struggling with externs for react-navigation, specifically this:

js
const Stack = createStackNavigator();

function App() {
  return (
    <NavigationContainer>
      <Stack.Navigator>
        <Stack.Screen name="Home" component={HomeScreen} />
      </Stack.Navigator>
    </NavigationContainer>
  );
}

can you give me a hint how I write this in haxe externs?

answering my own question: this mostly naive implementation works:

haxe
@:jsRequire('@react-navigation/native','NavigationContainer')
extern class NavigationContainer extends ReactComponentOfProps<ViewProps> {}

@:jsRequire('@react-navigation/stack','createStackNavigator()')
extern class Stack extends ReactComponentOfProps<ViewProps> {}

@:native('Stack.Navigator')
extern class StackNavigator extends ReactComponentOfProps<ViewProps> {}

@:native('Stack.Screen')
extern class StackScreen extends ReactComponentOfProps<{name:String, component:Dynamic}> {}

Yep, should do You can add static vars to Stack with a type of

ReactTypeOf<{...props...}>

too if you want to use Stack.Navigator (assuming you're using react-next?)

@quick-salesclerk-81994 I think there's already externs for react navigation