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

    user

    01/17/2020, 4:38 PM
    (btw extending twice a ReactComponent should now result in a proper error)
  • a

    ambitious-knife-25690

    01/17/2020, 4:48 PM
    What a bitter sweet fix 😂
  • a

    ambitious-knife-25690

    01/19/2020, 9:07 PM
    just a headsup
  • a

    ambitious-knife-25690

    01/19/2020, 9:07 PM
    mui + react-next break on latest nightly
  • a

    ambitious-knife-25690

    01/19/2020, 9:08 PM
    possibly router as well
  • u

    user

    01/20/2020, 8:17 AM
    Err
  • u

    user

    01/20/2020, 8:17 AM
    Break how?
  • u

    user

    01/20/2020, 8:22 AM
    Oh.. structInit.. yeah that change sucks
  • u

    user

    01/20/2020, 8:26 AM
    Pushed a fix to mui, the rest seems fine
  • a

    ambitious-knife-25690

    01/22/2020, 9:14 PM
    Will double check in a bit, downgraded back to regular for the time being
  • a

    ambitious-knife-25690

    01/22/2020, 9:14 PM
    I'm getting
    (e : { target : { value : Null<String> } }) -> Void should be Null<react.types.HandlerOrVoid<react.types.ClassicHandler>>
    but my code seems fine
  • a

    ambitious-knife-25690

    01/22/2020, 9:15 PM
    Copy code
    jsx
    <TextField 
      type={Date}
      value=${this.state.date}
      onChange=${(e) -> this.setState({date: e.target.value})}
      onKeyPress=${(e) -> if (e.key == "Enter") this.submitDate()}
    />
  • a

    ambitious-knife-25690

    01/22/2020, 9:15 PM
    onChange=${(e) -> this.setState({date: e.target.value})}
    for this line
  • a

    ambitious-knife-25690

    01/22/2020, 9:16 PM
    typedef ClassicHandler = Event->Void;
  • b

    brainy-machine-50829

    01/22/2020, 9:21 PM
    The only thing that comes to mind is
    Event
    not having
    target.value
    on it.
  • a

    ambitious-knife-25690

    01/22/2020, 9:30 PM
    lol
  • a

    ambitious-knife-25690

    01/22/2020, 9:30 PM
    it actually doesn't
  • a

    ambitious-knife-25690

    01/22/2020, 9:30 PM
    The reason why it worked in the other places i've used the code is cause I typed it dynamic
  • a

    ambitious-knife-25690

    01/22/2020, 9:32 PM
    onChange=${(e:Dynamic) -> this.setState({date: e.target.value})}
    ugly but it will work lol
  • b

    brainy-machine-50829

    01/22/2020, 9:32 PM
    Dynamic is dangerous. 😛
  • b

    brainy-machine-50829

    01/22/2020, 9:32 PM
    But often necessary with JS. 😦
  • a

    ambitious-knife-25690

    01/22/2020, 9:32 PM
    e.target.value is a normal thing
  • a

    ambitious-knife-25690

    01/22/2020, 9:32 PM
    for mui anyway
  • u

    user

    01/23/2020, 8:15 AM
    It should work if you type
    e
    as
    Event
  • u

    user

    01/23/2020, 8:15 AM
    Type inference has some trouble with mui event handlers
  • u

    user

    01/23/2020, 8:16 AM
    Though yeah, it doesn't have target.value..
  • u

    user

    01/23/2020, 8:18 AM
    I should start typing all that more strictly with
    SyntheticEvent<InputElement>
    and such, but since with mui you can choose what html element is used this won't be perfect for all use cases either
  • n

    numerous-oil-90946

    01/28/2020, 7:25 AM
    Hey everyone, do you know any tutorial for haxe react?
  • n

    numerous-oil-90946

    01/28/2020, 7:25 AM
    I am trying to use there exemple as a base but I got in browser console a React not defined
  • c

    cool-psychiatrist-49311

    01/28/2020, 7:34 AM
    are you using
    -D react-global
    ?
1...363738...80Latest