https://linen.dev logo
Powered by
# react
  • b
    Probably better now.
  • a
    Klabz has done a super job
  • b
    So how are you compiling the react? I remember you had the same issue with react-tools, Klabz doesn't use them, you hacked the error with some eslinter command or something, but are you still using react-tools?
  • b
    I wonder if there's something simpler maybe. I don't like the dark hole of node_modules it creates. 😄
  • a
    I was never really using react-tools
  • a
    well, not intentionally
  • a
    --macro includeFile('no-linting.js')
    In the 
    .hxml
  • b
    Oh hah, that's a nice trick.
  • a
    and in 
    no-linting.js
    add 
    /* eslint-disable */
  • a
    nice and simple x)
  • b
    Yeah. Still annoying though, but works.
  • b
    Meh, I probably won't ever make a decision. 😄
  • a
    I think a nice compromise would be getting some of the fun macro features of coconut into regular react
  • a
    At least with react-next if there's macro errors they don't come out of no where, with coconut they just always seem to come out of no where
  • a
    Even if the errors don't make sense, they're there for a reason lol
  • b
    I don't really know react much either, so as for QOL things, I have no clue.
  • a
    not needing to define a 
    State
    is nice
  • a
    also not needing to call 
    this.state...
  • b
    Yeah.
  • b
    Both have sort of top-down data flow though.
  • a
    Also no need to make each field in 
    State
    nullable
  • b
    Which at first I liked, then my app got bigger and it was annoying, changing bunch of classes just to pass more data below.
  • b
    Then I read about redux. Sounded perfect.
  • b
    I stopped with that app for 2 years.
  • a
    hah
  • b
    Now I'm reading redux is bad.
  • a
    Router works nicely
  • b
    I don't even know what that is. 😄
  • a
    I've never used redux though
  • a
    I am the opposite
1...333435...80Latest