• ByteJunk@lemmy.world
    291·
    2 年前

    I spent way too long today figuring out why my app was doing something that it’s NOT supposed to do on weekends.

    I read Luxon’s docs (pretty cool lib tbh) again and again, and tried everything I could think of to get isWeekend to return a sane result.

    Turns out I was pulling a somewhat older version of Luxon, where isWeekend didn’t exist. In any sane language, I expect I’d get a huge warning about a property that doesn’t exist, but alas…

    Typescript helps me keep my sanity, but juuuuust barely.

    • mynameisigglepiggle@lemmy.world
      211·
      2 年前

      If isWeekend doesn’t exist, then the weekend doesn’t exist, so it’s naturally false.

      That’s why JavaScript gets pushed so hard - it’s part of the capitalist agenda to keep us working 7 days a week

        • shastaxc@lemm.ee
          21·
          2 年前

          Falsy* because it was undefined

          However, their IDE should have highlighted it as an unknown property. Guess this guy is coding in notepad or vi.

          • humbletightband@lemmy.dbzer0.com
            2·
            2 年前

            Yep, thanks for correcting me. In fact, if they write something like

            if (day.isWeekend) {...}

            The block will never be executed with the old version of library

            • shastaxc@lemm.ee
              2·
              2 年前

              Yeah that’s exactly what I think happened to him. He needs a better IDE and/or needs to stop copy/pasting code from stackoverflow or documentation that doesn’t match his library version.

              • ByteJunk@lemmy.world
                11·
                2 年前

                My dude, you need to understand that all that anger and resentment, it is not you. It’s the years of JavaScript poisoning your mind.

                In any case, that goes to my point. I would have to be saved by my IDE, when any sane language will blow up in your face as soon as you try to run it.