https://linen.dev logo
Join Discord
Powered by
# react
  • a

    ambitious-knife-25690

    03/03/2020, 2:49 PM
    It's working fine now
  • a

    ambitious-knife-25690

    03/03/2020, 2:49 PM
    I don't get this shit
  • a

    ambitious-knife-25690

    03/03/2020, 5:14 PM
    i'm legit getting trolled
  • a

    ambitious-knife-25690

    03/03/2020, 5:14 PM
    didn't even touch that part of the code
  • a

    ambitious-knife-25690

    03/03/2020, 5:14 PM
    MACRO IT IS lol
  • u

    user

    03/04/2020, 6:32 AM
    Did you try the static var trick?
  • a

    ambitious-knife-25690

    03/04/2020, 9:27 AM
    I didn't because I'm not using webpack and it didn't seem like a good idea to add the dependency to an extern rather than just have a macro in the hxml
  • u

    user

    03/04/2020, 9:38 AM
    Oh ok
  • u

    user

    03/04/2020, 9:38 AM
    I don't know what the equivalent (of Webpack.require) is when using react-native
  • u

    user

    03/04/2020, 9:44 AM
    @ambitious-knife-25690 For troubling imports like that, have you considered making a separate JS imports file and using
    includeFile
    to prepend it to the output?
  • a

    ambitious-knife-25690

    03/04/2020, 9:45 AM
    That's what I've done
  • u

    user

    03/04/2020, 9:46 AM
    Oh. I thought you were just
    jsRequire
    -ing it
  • u

    user

    03/04/2020, 9:46 AM
    Ah, reading is a gift
  • a

    ambitious-knife-25690

    03/04/2020, 9:47 AM
    It's just for the best extern experience I would have preferred to avoid that, rnfirebase changed the way they structure their npm module so I've been trying to figure out a way to avoid this method... 2 secs
  • a

    ambitious-knife-25690

    03/04/2020, 9:47 AM
    https://github.com/Jarrio/haxe-react-native-firebase/blob/master/README.md#501539217327915038-native
  • a

    ambitious-knife-25690

    03/04/2020, 9:49 AM
    It's just sometimes the js require way worked
  • a

    ambitious-knife-25690

    03/04/2020, 9:49 AM
    And sometimes it wasn't lol
  • u

    user

    03/11/2020, 10:03 AM
    Should react-next start using scoped defines? (
    -D react.xx
    ) I don't expect many people to use it with haxe < 4, but that'd be a hard dependency on haxe 4+ =/
  • u

    user

    03/11/2020, 10:04 AM
    Should react-next start using scoped defines? (
    -D react.xx
    ) I don't expect many people to use it with haxe < 4, but that'd be a hard dependency on haxe 4+ =/
  • u

    user

    03/11/2020, 10:05 AM
    (sorry if message has been sent twice, I got some network issues)
  • b

    bitter-family-72722

    03/11/2020, 10:15 AM
    isn't this react-next thing only for the early-adopter kind of people anyway?
  • b

    bitter-family-72722

    03/11/2020, 10:15 AM
    you'd think they'd be on latest Haxe
  • u

    user

    03/11/2020, 10:16 AM
    Mostly yeah, but atm it's still compatible with haxe 3.4.x
  • a

    ambitious-knife-25690

    03/11/2020, 1:09 PM
    scoped defines may be cool, assuming they are what I think they are
  • a

    ambitious-knife-25690

    03/11/2020, 1:09 PM
    what benefit do you see for it specifically?
  • a

    ambitious-knife-25690

    03/11/2020, 1:10 PM
    Also as a side question: Is there a way to allow a property to accept both a function returning a jsx element and a straight ReactComponent?
  • a

    ambitious-knife-25690

    03/11/2020, 2:13 PM
    found it
  • a

    ambitious-knife-25690

    03/11/2020, 2:13 PM
    ReactType
    😁
  • u

    user

    03/12/2020, 6:34 AM
    Yep, ReactType :)
  • u

    user

    03/12/2020, 6:35 AM
    Scoped defines are
    -D react.xx
    , that's just a cleaner way of defining library-specific defines but that only works on haxe 4+ (doesn't parse on haxe < 4)
1...444546...80Latest