This is not so much a jsdoc error as a weird / stupid behavior (imo)
createBindingContext can apparently return in some case undefined (technically null based on the implementation) however when writing code this will never happen except when you do some weird thing.
It implies that resolve returns undefined (which btw is not in the signature) which would only happen if you have a relative binding without a parent context defined...
So ok it could happen but you'd be really looking for trouble writing such code :)
I wonder if it really makes sense to return undefined at all or if you should have an unresolveable context of some kind in there somewhere.
This is not so much a jsdoc error as a weird / stupid behavior (imo)
createBindingContext can apparently return in some case undefined (technically
nullbased on the implementation) however when writing code this will never happen except when you do some weird thing.It implies that resolve returns undefined (which btw is not in the signature) which would only happen if you have a relative binding without a parent context defined...
So ok it could happen but you'd be really looking for trouble writing such code :) I wonder if it really makes sense to return undefined at all or if you should have an unresolveable context of some kind in there somewhere.