-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Array.prototype.filter.not.forcing.boolean #7779
Array.prototype.filter.not.forcing.boolean #7779
Conversation
Hi @NimaZahedi, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution! The agreement was validated by Microsoft and real humans are currently evaluating your PR. TTYL, MSBOT; |
Missing baseline file... run these commands:
|
@RyanCavanaugh Ok, but isn't the same as #7776? 😕 |
@NimaZahedi Ryan means that we shouldn't even have generated an error baseline given your change. @yuit does the test harness use the LKG's libs? |
Ping @yuit - which files are the correct ones to edit? |
@RyanCavanaugh @DanielRosenwasser
|
@DanielRosenwasser the harness will pick up lib files built to |
@yuit I'll do, sure. thanks :) |
@yuit Should I write test case for every single of those types? (I mean the interfaces whose filter method is changed) |
👍 No need to write a test for every overload |
👍 |
@NimaZahedi look goods :) Thanks! |
Fixes #
Changed the return value of Array.prototype.filter, use any instead of boolean!
based on this issue: #5850