DEV Community


Discussion on: 😲🤯The most outstanding new feature in Javascript you need to know about: Optional Chaining

lampewebdev profile image
Michael "lampe" Lazarski Author

I would say that the objects you are getting are not well designed.

If you need to check that often that it will be a problem.

I mean you can overdo everything, adding 200 npm packages even if they just do small things would also be a bad pattern. In the end, it is in your fingertips to decide.

Thread Thread
chrisachard profile image
Chris Achard

Right, yep - if you're constantly checking the same thing for null or not, then maybe you need to abstract that to give you a better framework/way to access it.

Thread Thread
lampewebdev profile image
Michael "lampe" Lazarski Author

Like always thinking is the key here 😉

Thread Thread
qm3ster profile image
Mihail Malo

IMO it lends itself to patterns like:


Not only are you doing extra branching, but by having defaults at the usage site instead of defaults site you could have inconsistencies.

Instead, on construction of the this, you could have, incomingData)

and then access all the properties unconditionally.
(You could also only merge in properties that already exist in defaultData tree, and perform validation at this stage, creating a very predictable this)