https://linen.dev logo
Join Discord
Powered by
# react
  • a
    Just a simple getter
  • a
    for now i'm just getting around the issue by just `"haxe.enableCompilationServer": false`lol
  • u
    Oh sorry missed your answer You may need to type this as 
    ReactFragment
    (for example with an 
    inline function getGoodHours():ReactFragment return good_hours
    )
  • a
    This error is now appearing on projects that never had the issue before
  • a
    (Just went back to an old project)
  • a
    disable all the compilation servers
  • a
    \o/
  • c
    Lock your compiler version and library versions with lix and you will able to go back to old projects exactly as they were 😉
  • a
    I like using the latest stuff for the most part where possible
  • a
    if there are things to port forward I would like to know
  • a
    plus if everyone did that, how would we find bugs with new versions? xD
  • u
    Just wait for someone to start a project with new version :D
  • u
    But they might just give up or use an older version if there are bugs, so that wouldn't work so well x)
  • a
    I defo think that's what would happen 😂
  • a
    I remember dropping haxe like 3 times when I first heard about it because of setup issues
  • u
    That's not an issue though, we all have perfect test suites o/
  • u
    Oh wait :D
  • u
    Tbf I also "lock" my haxe & library versions (only upon installation) but keep updating them all the time
  • a
    I just install everything from git lol
  • u
    Being locked as in "last compiled with these" doesn't mean you don't update things
  • u
    What could go wrong? :D
  • u
    Worst case scenario it doesn't work, so what? I'll just work on this project another day when it does o/
  • a
    These kind of conflicts only happen with macro heavy stuff, fortunately I don't use macros much myself
  • u
    Well... you're using react-next, so you are xD
  • a
    Maybe unfortunately as well, if i were more versed in macros I could probably spend time debugging more than being the guy who just shouts "bug over here" lol
  • u
    Though latest git versions of react-next and material ui should always be compatible
  • a
    Maybe I'm not on the latest :o
  • u
    But when you add other libs, it might not
  • u
    Diagnostics can very well be broken though, I don't use that x)
  • u
    I'm not even sure they worked properly with react-next at some point
1...525354...80Latest