You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please consider add support for expose property in new createError.[code || name]([msg])) like syntax.
We use new createError.name([msg])) a lot because of its readability. It also mitigates the need to remember all those status codes. Being able to do something like below will be of great help.
varerr=newcreateError.NotFound("Show this error to client.",{expose: true, ...});
The text was updated successfully, but these errors were encountered:
Thanks for the suggestion @maneetgoyal . This will be included in the upcoming 3.0 release as it provides an update to align to the new options feature of the global Error constructor.
Hi all,
Please consider add support for
expose
property innew createError.[code || name]([msg]))
like syntax.We use
new createError.name([msg]))
a lot because of its readability. It also mitigates the need to remember all those status codes. Being able to do something like below will be of great help.The text was updated successfully, but these errors were encountered: