-
Notifications
You must be signed in to change notification settings - Fork 542
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
Fix isAlien to properly identify built-in functions. Partially fixes #18244 #123
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Use
Boolean(it)
instead of!!it
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've never heard that rule before. The current syntax is terser.
I have a more basic objection though. The function no longer does what it says. The summary (emphasis added) is
Now you've changed it to only report things that do report as functions. Why is that?
Also, the ticket (https://bugs.dojotoolkit.org/ticket/18244) says something about _toArray(), but you haven't changed anything with toArray().
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think Boolean() is the preferred syntax for TS and ES6, but I agree that it doesn't really matter here, and !! is far more commonly used in Dojo 1.x.
I agree with the other points made. I was trying to figure out if the intent was really to change the second condition to be the opposite of what it is today, or if the real issue is to just make it be guaranteed to be truthy?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Judging from the text in https://bugs.dojotoolkit.org/ticket/18244, and also by @mlabrec's initial comment to this PR "Also made the function return bool for falsy arguments.", I think the main point was to change the
!isFunction()
toisFunction()
.And I assume that's because the bug/PR author didn't carefully read the spec for what
isAlien()
is supposed to do. It's calledisAlien()
, notisNativeOrNormalFunction()
.