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.

Sign up for GitHub

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

Jump to bottom

Recognize iterating functions as fors when that's the case. #39

Open
S2dentik opened this issue Nov 21, 2016 · 0 comments
Open

Recognize iterating functions as fors when that's the case. #39

S2dentik opened this issue Nov 21, 2016 · 0 comments

Comments

@S2dentik
Copy link
Contributor

The developer can easily write forEach or map instead of for-in statements to get rid of warnings and code smells. Taylor should be able to handle these cases appropriately.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@S2dentik