proposal-nullish-coalescing

For comparison, here are the Javascript RFCs for the equivalent operators: https://github.com/TC39/proposal-optional-chaining https://github.com/tc39/proposal-nullish-coalescing IMO optional chaining is a lifesaver when dealing with deeply nested JSON, and it's become indispensable in our Typescript code. But we also deal with JSON from various third-party endpoints in Python, and far too often we resort to an inefficient deep_get utility to make our code sensical. > if json?.get("foo")?.get("bar")?[0]?.get("baz") may seem messy but would be infinitely better than the fragile (note the nested list-of-a-single-dict, and how bugs can appear if it's not there): > if json.get("foo", {}).get("bar", [{}])[0].get("baz") or the inefficient > if deep_get(json, "foo.bar.0.baz") It's not nearly as good as the Typescript json.foo?.bar?.[0]?.baz - but

This may feel a bit nit-picky, but they haven't been added to ECMAScript yet. There are two features here: the optional chaining operator[1] and nullish coalescing operator[2]. Both are at stage 3 of the standardization process. Changes to proposed features can still be made at stage 3 if critical issues come up. Otherwise, once implementors have sufficient experience with them (and tests & multiple implementations exist) the proposals will be eligible to move to stage 4, after which they'll be able to be included as part of the next ECMAScript spec. Both proposals are progressing through the process very smoothly, but I wouldn't rely on them for anything critical just yet. [1] https://github.com/tc39/proposal-optional-chaining [2] https://github.com/tc39/proposal-nullish-coalescing

Yep. Both are stage-1 proposals: https://github.com/tc39/proposal-optional-chaining https://github.com/tc39/proposal-nullish-coalescing Recently started using optional chaining in our codebase (via Babel 7) and it's great so far. Also gives us proper static typing safety unlike Lodash `get(...)`