Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[prefer-tacit] should not consider as error when the user intentionally skipped some parameters

See original GitHub issue

Bug Report

test.ts:

const a = ['1', '2']
a.map((x) => parseInt(x))
// result: [1, 2]

Expected behavior

No eslint error

Actual behavior

prefer-tacit error, and autofixed to the following code which does not work because parseInt takes a second parameter radix and it should not be an index

test.ts:

const a = ['1', '2']
a.map(parseInt)
// result: [1, NaN]

Steps to reproduce

Code mentioned above, running in eslint-plugin-functional v4.4.0 with rule 'functional/prefer-tacit': 'error'

Proposed changes

Do not consider it as error when the user intentionally skipped some parameters

Issue Analytics

State:
Created a year ago
Comments:5

Top GitHub Comments

1reaction

github-actions[bot]commented, Oct 3, 2022

🎉 This issue has been resolved in version 4.4.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

1reaction

RebeccaStevenscommented, Sep 30, 2022

Alright, I’ll look into it.

Top Results From Across the Web

eslint-plugin-functional's Language Statistics - Codesti

[prefer-tacit] should not consider as error when the user intentionally skipped some parameters, closed, 5 ; Action Required: Fix Renovate Configuration, closed ...