https://linen.dev logo
Join Discord
Powered by
# react
  • u
    Strange, I have done that with all kind of components for all versions of react-router from 4.0.0 to 5.1.2
  • u
    What does console.dir(SystemLogs) print?
  • a
    @User
  • u
    Uh.. using coconut?
  • u
    I haven't tested with coconut, and I'm not sure everything works fine with it =/
  • a
    Coconut is in the project but i'm not using it as I couldn't figure out how to use it with mui xD
  • u
    Seems to be getting in the way anyway x)
  • a
    which is very unusual :D
  • a
    I figured dce would tell it to go away
  • u
    Yeah, not like it's macro-heavy :D
  • u
    It's probably coconut that breaks the component prop in react-router
  • a
    Fair
  • a
    As much as I want to use coconut I am still scared of it so it's an easy thing to convince me to remove 😂
  • u
    It does alter SystemLogs anyway, or did you add fromHxx yourself?
  • a
    I didn't add that myself
  • u
    What version of react-next are you using?
  • a
    It's the git version
  • a
    it has 
    "version": "1.119.0",
    in the haxelib.json don't know if you have that up to date with git
  • a
    also removing coconut and the error still remains
  • u
    Hmm.. what haxe react-router are you using? react-router-4, right?
  • u
    The haxe one
  • a
    "version": "0.2.8",
    in the haxelib
  • a
    but installed from github
  • u
    Yeah seems like the good one
  • a
    Why dont macro errors link to the line that is causing the issue
  • a
    I've looked everywhere that could be related to this and nothing is clear :/
  • b
    that's an issue with the macro
  • a
    😂
  • b
    it's the macro's responsibility to give an error position
  • b
    Which is honestly a lot of work sometimes, and not always simple to do.
1...303132...80Latest