Great notes!
If I may add: regarding to classes you might want to try something like this if you want to accept an options like constructor
classSomeClass{constructor(options){Object.assign(this,options);// if you want required properties you may want to if check here// and throw if required props are not present}toString(){returnObject.entries(this).map(([key,value])=>`[${key}: ${value}]`).reduce((last,current)=>`${last?`${last}, `:''}${current}`,'')}}constsome=newSomeClass({propA:'this is a',propB:'this is b'});some.toString();//"[propA: this is a], [propB: this is b]"
of course if you are using typescript you can extend that to use an interface and ensure you only accept what is required.
it is pretty useful, I think it has become better to work with collections, if you have teamates with python background, they can easily recognize [...someIterable] also it lets you do some stuff like const keys = [...Object.keys(myObj)] without for in or for each
also for people that isn't too much into functional methods like map, reduce, ans such, for of is quite a savior.
on the protocol vs interface, I think protocol is better suited in jsland where interfaces only exist on agreements (which some times not everyone agrees the same thing), not enforced in code.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Great notes!
If I may add: regarding to
classesyou might want to try something like this if you want to accept an options like constructorof course if you are using typescript you can extend that to use an interface and ensure you only accept what is required.
What are your thoughts on
iteratoras a protocol and not an interface?it is pretty useful, I think it has become better to work with collections, if you have teamates with python background, they can easily recognize
[...someIterable]also it lets you do some stuff likeconst keys = [...Object.keys(myObj)]withoutfor inorfor eachalso for people that isn't too much into functional methods like map, reduce, ans such,
for ofis quite a savior.on the protocol vs interface, I think protocol is better suited in
jslandwhere interfaces only exist on agreements (which some times not everyone agrees the same thing), not enforced in code.