Optional chaining and more in path notation

[nlepage]

Description

Add optional chaining operator in path notation :

const obj = { a: { b: {} } }
set(obj, 'a?.b.c', 1) // => { a: { b: { c: 1 } } }
set(obj, 'a?.c.b', 1) // => returns obj reference

Also add a null check operator :

const obj = { a: { b: {} } }
set(obj, 'a!.b.c', 1) // => { a: { b: { c: 1 } } }
set(obj, 'a!.c.b', 1) // => throws TypeError

The default behavior would stay "lodash like", that is failsafe and do the best we can.
The "do the best we can" is to be defined depending on the case.

As suggested by @EmrysMyrddin it would be nice to have a way of changing the default behavior, for example turn all of immutadot in null check mode.

[nlepage]

@frinyvonnick @hgwood @EmrysMyrddin @charlyx
What do you think ? This is open for debate 😉

[nlepage]

Also optional chaining is in stage 1 : tc39/proposal-optional-chaining

[hgwood]

Looks really cool! 💯 Could you add some more examples to cover the following cases so we can have a broader view of impacts?

• array notation
• access to properties ending with ? and !

The obvious downside is the increasing complexity of the path syntax and associated parser, but I guess this syntax is one of the corner stone of the lib so I'm OK with it.