Skip to content
This repository was archived by the owner on Jan 6, 2025. It is now read-only.

chore: use a for loop instead Array.map() when the return value is discarded. #469

Closed
wants to merge 2 commits into from

Conversation

bowenni
Copy link
Contributor

@bowenni bowenni commented Oct 24, 2017

We're enabling a check in google's internal TypeScript compiler that detects calls to well-known functions and methods that return a value that is discarded. So this pattern will become a compilation error soon.

@bowenni
Copy link
Contributor Author

bowenni commented Nov 1, 2017

Ping :)

@bowenni bowenni requested a review from matsko November 8, 2017 04:45
@bowenni bowenni changed the title chore: use Array.forEach() instead Array.map() when the return value is discarded. chore: use a for loop instead Array.map() when the return value is discarded. Nov 11, 2017
@bowenni bowenni requested a review from alexeagle November 22, 2017 17:33
@ThomasBurleson ThomasBurleson added this to the v2.0.0-beta.13 milestone Nov 29, 2017
@ThomasBurleson ThomasBurleson added build P1 Urgent issue that should be resolved before the next re-lease labels Nov 29, 2017
@bowenni
Copy link
Contributor Author

bowenni commented Dec 11, 2017

Ping

@ThomasBurleson
Copy link
Contributor

ThomasBurleson commented Dec 14, 2017

@bowenni - Thanks, this will be in Beta.12. I am merging this now.

@ThomasBurleson ThomasBurleson modified the milestones: v2.0.0-beta.13, v2.0.0-beta.12 Dec 14, 2017
atscott pushed a commit to atscott/flex-layout that referenced this pull request Feb 3, 2018
When the `Array.map()` results are discarded, use `Array.forEach()`.

Google's internal TypeScript compiler that detects calls to well-known functions and methods that return a value that is discarded. So this pattern will become a compilation error soon.

Fixes angular#469.
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
build cla: yes P1 Urgent issue that should be resolved before the next re-lease
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants