Always doing o.assign({},…); is a good enough level of care, imo.

…ng object rather than creating a new object is usually a bug. At the very least, it is error-prone. Be careful with Object.assign().

Feb 25, 2017 · 1 min read

Written by

Randy MacDonald

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch

Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore

Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade