use optional chaining in the type guard for greater safety

[suddjian]

The generated is{entryName} functions are only useful if you're confident that the thing you're passing in is, at least, a fully-fleshed-out Entry type. But it's possible to not know what exactly you have. In my case, I have a situation where my object is either a string, an unresolved link, or one of three entry types. And in that case the caller of is{entryName} will need to do additional checks to make sure it's even safe to call this function, or risk throwing an exception. Better to have the function just behave safely and do its job all the way.

As a general practice in TS, isXYZ functions should be safe to call with any argument.

[marcolink]

Hi @suddjian 👋
Thanks for your contribution 🙏 . Can you please add a description to the PR and some reasoning behind the requested change? Would love to see the use cases.

[suddjian]

I added some more information. Please do let me know if there's any other clarification I can provide.

[suddjian]

Any chance of merging this?

[marcolink]

#346

[marcolink]

@suddjian version 2.15.2 comes with your changes - have a nice weekend!