Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Rudy Ges
    @kLabz
    My view on this is as long as it's not too much trouble I might as well keep supporting haxe 3
    If you have good reasons to drop it, then I guess I'd be happy to have an excuse to stop worrying about it x)
    I'm not even sure anyone is using react-next with haxe < 4
    Thomas F├ętiveau
    @zabojad
    I am :p
    Axel Huizinga
    @axelhuizinga
    Is there any example of server side rendering react with haxe?
    Philippe
    @elsassph
    I had started a sample project but it's tricky: you need to have a node server and there's a million options.
    Axel Huizinga
    @axelhuizinga

    Recently I see this kind of warnings - do we have to change the function names in ReactComponent.hx?
    Warning: componentWillUpdate has been renamed, and is not recommended for use. See https://fb.me/react-async-component-lifecycle-hooks for details.

    • Move data fetching code or side effects to componentDidUpdate.
    • Rename componentWillUpdate to UNSAFEcomponentWillUpdate to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE name will work. To rename all deprecated lifecycles to their new names, you can run npx react-codemod rename-unsafe-lifecycles in your project source folder.

    Please update the following components: Connect(UiView)

    Vladimir Cores
    @dqvsra_twitter
    Hey! Whats up people? : )
    Axel Huizinga
    @axelhuizinga

    Help - 2 days now looking for the reason of this error (code has been working well b4 but can't find what changed)

    view/dashboard/Settings.hx:componentDidCatch:40:TypeError: _this is undefined Out.hx:156
    view/dashboard/Settings.hx:componentDidCatch:41:{
    componentStack :
    in User (created by Settings)
    in Settings (created by Route)
    ...

    How can I locate the _this reported to be undefined?

    Rudy Ges
    @kLabz
    Running on haxe nightlies? What's in Out.hx:156?
    Axel Huizinga
    @axelhuizinga

    Running on haxe nightlies? What's in Out.hx:156?

    something completely unrelated within an #elseif flash codeblock on a js target... I guess some error in my jsx code caused the weird issue - anyway ok now again

    Axel Huizinga
    @axelhuizinga

    I had started a sample project but it's tricky: you need to have a node server and there's a million options.

    Philippe is your project code still available?

    Axel Huizinga
    @axelhuizinga
    Is there any docs or example for using haxe-apollo?
    Rudy Ges
    @kLabz
    Nope.. I could add some code snippets as "doc"
    1 reply
    Axel Huizinga
    @axelhuizinga
    will be very much appreciated :) any plans about apollo server?
    Rudy Ges
    @kLabz
    None, I don't even know what it does
    Axel Huizinga
    @axelhuizinga
    From their site: Apollo Server is an open-source, spec-compliant GraphQL server that's compatible with any GraphQL client, including Apollo Client. It's the best way to build a production-ready, self-documenting GraphQL API that can use data from any source
    Rudy Ges
    @kLabz
    Well yeah, no plan at all, I'm using dotnet for the API side
    Philippe
    @elsassph
    @axelhuizinga sorry missed your question - I realised my WIP still only had the client side, not SSR. It's a rather complex problem to get right TBH.
    Axel Huizinga
    @axelhuizinga
    after upgrading haxe to 4.1.1 my ReactComponent classes fail to compile with:
    Cannot access field or identifier state for writing
    Rudy Ges
    @kLabz
    Seems like you're using state on a component declared as stateless
    I'll double check locally though
    Damn I actually reproduce..
    Rudy Ges
    @kLabz
    Released 1.121 with a "temp" fix, and opened HaxeFoundation/haxe#9552 to look for a real solution
    Now I have another issue on my project, I hope it doesn't affect all react-next projects..
    Rudy Ges
    @kLabz
    acceptsMoreProps, aria-x props, etc. are (temporarily) broken too =/
    Philippe
    @elsassph
    Big deal LOL
    Axel Huizinga
    @axelhuizinga
    I would appreciate some advice on creating a NumberFormat Component for react - is there already a haxe extern or more generally a pattern to create such compatible with this design:
    var NumberFormat =
    /*#__PURE__*/
    function (_React$Component) {
      _inherits(NumberFormat, _React$Component);
    
      function NumberFormat(props) {
        var _this;
    Philippe
    @elsassph
    Where does that comes from? It looks like an old-school JS pseudo-class pattern.
    Axel Huizinga
    @axelhuizinga

    https://github.com/s-yadav/react-number-format/blob/master/lib/number_format.js - after looking at the src version I found the usual

    @:jsRequire('react-number-format', 'default')
    extern class NumberFormat extends ReactComponentOfProps<NumberFormatProps>{}

    seems to work well