in my opinion it is good practice
but maybe 75% of === is not necessary
it is always better to have === habit
but in real life if you want to measure that your code will work without === kind of 75% will work with == too
"this" == 'this' ?
'this' === "this" ?
of course, but i suggest to always check types by yourself
if ( typeof someVar === 'number' ){}
you will have more information why your code doesn't work
but if you if( someVar === 10 )
you don't have that information, you have only information that someVar does not equal 10 it can be string and you don't know that so you are wasting your time to find out why my code doesn't work?
oooh c'mon...
even Angular convert functions to strings and parse it...
it can be anything - but comments are good thing for programmers and now they can have another functionality added
comments role is to be transparent but why not use if you can
and if its easy, you don't need to compile it like coffee or typescript. and code is clear without a hustle.
but if you really don't want to use comments you can use object declarations instead. there is no need for using comments in clsjs but it is easier and better way I think.
of course you can disagree - that is your point of view and everything is ok.
but I will think of your suggestion about string, that is also very good idea!
in my opinion it is good practice but maybe 75% of === is not necessary it is always better to have === habit but in real life if you want to measure that your code will work without === kind of 75% will work with == too "this" == 'this' ? 'this' === "this" ? of course, but i suggest to always check types by yourself if ( typeof someVar === 'number' ){} you will have more information why your code doesn't work but if you if( someVar === 10 ) you don't have that information, you have only information that someVar does not equal 10 it can be string and you don't know that so you are wasting your time to find out why my code doesn't work?