Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error messages for incorrect "in" and "new" operands always displays "undefined" as type #61

Closed
kpreisser opened this issue Oct 15, 2016 · 0 comments

Comments

@kpreisser
Copy link
Collaborator

Hi,
this is a follow-up issue to #59. The error messages for incorrect in and new operands always display undefined as actual type:

'toString' in 5;
// TypeError: The in operator expected an object, but found 'undefined' instead

new (String('five'));
// TypeError: The new operator requires a function, found a 'undefined' instead

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant