I understand people can start hating classes because of all that :)

And people freak out when the original lifecycle methods are touched - good riddance to

componentWillReceiveProps

but reactions have been heated

well, ok, if you use a dynamically typed language and APIs start moving under your feet you have every reason to freak out :D

And npm modules rot

As of now we have 95 occurences of

componentWillReceiveProps

in our codebase. And a lot of these functions are here to track props "transitions" as they compare previous and new props to decide whether state needs to be recalculated. This isn't going to be fun to refactor.

isn't that what getDerivedStateFromProps is for? ^^

This function doesn't give you the previous props, only new props and current state

And of course, because the codebase is a mess, we have a lot of sideeffects happening in

componentWillReceiveProps

\o/

The side effects will be fun x)

Is there a base project for using react-native + modular?

Oh, am I correct in that I don't have to bother with the libs.js folder with react-native?

@ambitious-knife-25690 react-native requires to build like a node application, e.g. without the

libs.js

and the

require

stub. This will happen if there is

-D nodejs

.

I didn't try whether that works though.

I will try to mess around with it and see if I can something working

So haxe-modular can't find

haxe-split

- I like to install npm modules in a /bin/node-modules could it be because I haven't ran installed npm haxe-modular in the project's root?

Yes it's expecting to find node_modules in the working directory

Alternative is to have

haxe-split

in the PATH I think

Anyway to change that configuration?

node modules, especially with a react native project makes for a very messy root dir ha

@ambitious-knife-25690 as I said, you can set the PATH to include

./bin/node_modules/.bin/

before running the Haxe compiler, or use the undocumented

-D haxe_split=/path/to/haxe-spit

https://github.com/elsassph/haxe-modular/blob/master/src/Split.hx#L51

haxe
const drawerWidth = 240;

const useStyles = makeStyles(theme => ({
  root: {
    display: 'flex',
  },
  appBar: {
    width: `calc(100% - ${drawerWidth}px)`,
    marginLeft: drawerWidth,
  },`
  drawer: {
    width: drawerWidth,
    flexShrink: 0,
  },

What is the conversion process of react code like? Particularly the style itself + the

appBar.width

code

I'm using k-labz material-ui

Hi, here's the small doc I gave to coworkers internally: https://gist.github.com/kLabz/20f6e4dece9aa4c256af58514626b66f Some needed classes are in mui.core.styles package MuiTheme currently has to be constructed on your end And I need to add special cases..

Added a comment there with another example

Thanks!

It looks like creating externs for react/react-native is more complicated with react-next

not sure how to proceed with externs now, there's so many

prop

classes etc

not saying it's bad, just overwhelming