• AzureDiamond (unregistered)

    what language is that code? function() => { } is not legal js or php as far as i know, either you use () => { } or function() { }without the arrow. might just be a typo but its wierd

  • Hanzito (unregistered) in reply to AzureDiamond

    It's Javascript, and as far as I'm concerned, JS in the backend is the real WTF. I would say: how could this not have happened at some point?

  • Angela (unregistered) in reply to AzureDiamond

    Pretty sure there's just a missing )

  • (nodebb) in reply to Hanzito

    it's not valid JavaScript. Traditional function syntax is function(params) { body }, ES6 arrow function syntax is (params) => { body }. You can't have both the function keyword and =>.

    But other than that it looks like pretty normal Node.js using the Express framework.

  • (nodebb)

    | why didn't this blow up the logs earlier?

    Would any regulars around here really be surprised at how often logging is misconfigured, disabled, or outright ignored? This probably blew up the logs because someone took a moment to fix the logging mechanisms.

  • (nodebb) in reply to RyanTG

    That wouldn't surprise me at all if that was the reason. Though it could also be that the code wasn't actually being called previously; perhaps based a condition that wasn't being met.

  • oyyo (unregistered)

    The real wtf is that JS can read/parse es5+es6 at the same time, so that looks valid to me.

    Their database probably was down or was getting hit with junk to get the next call to trigger, because why else would the next have not fired before

  • Kell Sønnichsen (unregistered)
    Comment held for moderation.

Leave a comment on “The Update Route”

Log In or post as a guest

Replying to comment #:

Log Out

« Return to Article