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
'TypeError: Cannot read property 'displayName' of null
at ...\node_modules\node-input-validator\lib\validator.js:248:22
at Array.map (<anonymous>)
at Validator.parseValue (...\node_modules\node-input-validator\lib\validator.js:244:14)
at Validator.apply (...\node_modules\node-input-validator\lib\validator.js:339:31)
at ...\node_modules\node-input-validator\lib\validator.js:209:29
at Array.forEach (<anonymous>)
at Validator.check (...\node_modules\node-input-validator\lib\validator.js:203:16)
at ...)'
This requires to add a specific check whether info is null before calling node-input-validator constructor which seems more of a crutch than a solution.
Could null inputs be treated as empty object to avoid the error above? Thanks.
P.S. node-input-validator version is 4.3.3
The text was updated successfully, but these errors were encountered:
Kavinkumar07
added a commit
to Kavinkumar07/node-input-validator
that referenced
this issue
Nov 26, 2022
Hi,
Please, consider the following rule for a some request input, let's say to update user settings:
Info is not required to be passed but if a client sends a payload as
Validator throws
This requires to add a specific check whether info is null before calling node-input-validator constructor which seems more of a crutch than a solution.
Could null inputs be treated as empty object to avoid the error above? Thanks.
P.S. node-input-validator version is 4.3.3
The text was updated successfully, but these errors were encountered: