TypeScript is basically the only reason I'm able to write JavaScript. At all. Everytime I interact with a JS library that doesn't have typings I'm reminded of this at a deep level. "protocol.include()" "protocol.include" is not a function" How the hell was I supposed to know that
Anyway just lost a day or two of time because
1. Writing callbacks/async functions
2. Something in the guts of the system calling the callbacks was catching exceptions and not printing the errors
3. Called a nonexistent function in a callback because there's no typings or docs
1. Writing callbacks/async functions
2. Something in the guts of the system calling the callbacks was catching exceptions and not printing the errors
3. Called a nonexistent function in a callback because there's no typings or docs
4. Invalid function call throws an exception, callback caller throws away the exception, my debug printf on the line after the invalid function is not printed
5. I assume, because the debug printf isn't seen, that the entire function is not being called
THIS HAS HAPPENED BEFORE
5. I assume, because the debug printf isn't seen, that the entire function is not being called
THIS HAS HAPPENED BEFORE
Alright. I am in a nightmare. Does anyone want to explain this to me.
I have what I *think* is an array. I console.log it and also its type. It says it's an "object" and then prints it out like it's an array.
I call .include(), a ECMAScript 7 method on arrays. it doesn't exist.
I have what I *think* is an array. I console.log it and also its type. It says it's an "object" and then prints it out like it's an array.
I call .include(), a ECMAScript 7 method on arrays. it doesn't exist.
If I were in Python, I'd understand this. I'd think: This is a non-array object which follows the iteration protocol. I need to convert it to an array with [x for x in protocols]. What is the most appropriate way to deal with this situation in JavaScript?
D: D: D: D: D: D: D: D: this was the problem
https://twitter.com/RReverser/status/1400151377922433024
Anyway I'll note this error was simple, silly, and "my fault" (1 letter typo). But various lang/ecosystem characteristics (no typings/docs, callback programming with the risk of a diaper pattern, odd duck type punning) made it a nightmare. I've been chasing this bug since Dec 12
• • •
Missing some Tweet in this thread? You can try to
force a refresh
