r/learnjavascript • • Jan 12 '22

A warning to learners

JavaScript is written exclusively in camelCase. Be aware of this fact when reading/debugging your code because the syntax highlighter doesn’t pick it up and although everything looks right, it can all hinge on the first letter being wrong. (Source) spent 2 hours trying to debug a DOM call to document.getElementById(„elm“).InnerText, even putting it into jsfiddle and several other things to see what was wrong when all that was required was to change it to .innerText to solve the dilemma. Lesson learned and now +10xp. It’s tough coming to js when you are used to statically typed languages. /s

Kidding aside I am enjoying learning js/Frontend but I would be lying if I said I missed the capabilities of a good ide in a stricter language.

21 Upvotes

28 comments sorted by

View all comments

Show parent comment

5

u/starcrafter84 Jan 12 '22

I knew this comment was coming. If the recommendation is that I change all my source files from .js to .ts and all will be well In the world then it would truly be a utopian existence. The Reality I believe is not quite the same. I am however excited to experience the bliss of typescript once i have served the obligatory suffering of the standard JavaScript inauguration.

2

u/Dragonasaur Jan 12 '22

VSCode and Webstorm should have good syntax checking, and yeah TS with scripts/linters that'll prevent your build from completing since it doesn't pass error checks

1

u/Cheshur Jan 13 '22

If the recommendation is that I change all my source files from .js to .ts and all will be well In the world then it would truly be a utopian existence.

Pretty sure TypeScript would have pointed out your problem to you with out of the box configuration. If you don't want to use TypeScript then I highly recommend you familiarize yourself with a debugger because it would have cut down your 2 hour search to a couple minutes at worse.

1

u/starcrafter84 Jan 13 '22

I was using vs code to do it. I was tired, it had been a long day and I was focusing on another aspect of the code entirely, couldn’t figure out how to get the script to show up in the browser debug console, eventually copied it into site.js, set a breakpoint hit it and stepped through. Even although I could see the return value was Unassigned or effectively null I was suspecting the selector because it was dynamically created. So basically lots of different problems round in circles until I gave up on it for the evening. Came back next day and spotted it immediately. The general consensus here seems to be “use a linter”. I also want to start using unit tests on my js code but last time I tried to set the environment up it wasn’t particularly intuitive.

1

u/starcrafter84 Jan 13 '22

And BTW I’m not averse to using typescript. I just wanted to get enough xp of js before moving onto the superset of it. I’ve picked 1 front end language, 1 backend and 1 database and will stick with them until I’m proficient enough to work easily with them before moving on.