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

util: fix iterable types with special prototype #25457

Closed
wants to merge 1 commit into from

Conversation

BridgeAR
Copy link
Member

The fallback should only be taken for a null prototype. If an
iterable data type (e.g., Array) has a prototype without
Symbol.iterator, just try the best to visualize it as object.

Fixes: #25451

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • tests and/or benchmarks are included
  • documentation is changed or added
  • commit message follows commit guidelines

@nodejs-github-bot
Copy link
Collaborator

@BridgeAR sadly an error occured when I tried to trigger a build :(

@nodejs-github-bot nodejs-github-bot added the util Issues and PRs related to the built-in util module. label Jan 11, 2019
@BridgeAR
Copy link
Member Author

@nodejs/util PTAL

@BridgeAR
Copy link
Member Author

BridgeAR commented Jan 16, 2019

The fallback should only be taken for a null prototype. If an
iterable data type (e.g., Array) has a prototype without
`Symbol.iterator`, just try the best to visualize it as object.

Fixes: nodejs#25451
@BridgeAR BridgeAR added the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label Jan 17, 2019
danbev pushed a commit that referenced this pull request Jan 18, 2019
The fallback should only be taken for a null prototype. If an
iterable data type (e.g., Array) has a prototype without
`Symbol.iterator`, just try the best to visualize it as object.

PR-URL: #25457
Fixes: #25451
Reviewed-By: Gus Caplan <me@gus.host>
Reviewed-By: Anto Aravinth <anto.aravinth.cse@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
@danbev
Copy link
Contributor

danbev commented Jan 18, 2019

Landed in 2c0a751.

Hope this was alright to land even though there was a pending request for @addaleax to review. I saw that @BridgeAR added the author-ready label which I took as sign that it was alright to merge. Let me know if this is not the case for future reference.

@danbev danbev closed this Jan 18, 2019
addaleax pushed a commit that referenced this pull request Jan 23, 2019
The fallback should only be taken for a null prototype. If an
iterable data type (e.g., Array) has a prototype without
`Symbol.iterator`, just try the best to visualize it as object.

PR-URL: #25457
Fixes: #25451
Reviewed-By: Gus Caplan <me@gus.host>
Reviewed-By: Anto Aravinth <anto.aravinth.cse@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
@MylesBorins MylesBorins mentioned this pull request Jan 24, 2019
@BridgeAR BridgeAR deleted the fix-inspect-clazz-issue branch January 20, 2020 11:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
author ready PRs that have at least one approval, no pending requests for changes, and a CI started. util Issues and PRs related to the built-in util module.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

TypeError: clazz is not a constructor on ≥ v11.6.0
6 participants