馃拝 lint/complexity/noForEach
should not throw on Effect.forEach
(or be configurable)
#3351
Open
1 task done
Labels
A-Linter
Area: linter
L-JavaScript
Language: JavaScript and super languages
S-Enhancement
Status: Improve an existing feature
S-Needs discussion
Status: needs a discussion to understand criteria
Environment information
Rule name
lint/complexity/noForEach
Playground link
https://biomejs.dev/playground/?code=aQBtAHAAbwByAHQAIAB7ACAARQBmAGYAZQBjAHQALAAgAFAAcgBlAGQAaQBjAGEAdABlACwAIABwAGkAcABlACAAfQAgAGYAcgBvAG0AIAAnAGUAZgBmAGUAYwB0ACcAOwAKAAoAYwBvAG4AcwB0ACAAYQByAHIAYQB5ACAAPQAgAFsAMQAsACAAMgAsACAAbgB1AGwAbAAsACAAMwBdADsAIAAKAAoAcABpAHAAZQAoAAoAIAAgAGEAcgByAGEAeQAsAAoAIAAgAEUAZgBmAGUAYwB0AC4AZgBvAHIARQBhAGMAaAAoAHgAIAA9AD4AIABQAHIAZQBkAGkAYwBhAHQAZQAuAGkAcwBOAG8AdABOAHUAbABsAGEAYgBsAGUAKAB4ACkALAAgAHsAIABjAG8AbgBjAHUAcgByAGUAbgBjAHkAOgAgACcAdQBuAGIAbwB1AG4AZABlAGQAJwAgAH0AKQAKACkACgA%3D
Expected result
The lint rule
lint/complexity/noForEach
is very useful for plain arrays, and I would like to enable it.I read the caveat on the rule page. In our codebase however, we use a lot of Effect, a functional programming library.
Effect.forEach
is used often enough that it would be bothersome to addbiome-ignore
comments to every usage.Would it be feasible to make this rule configurable to ignore some objects?
Code of Conduct
The text was updated successfully, but these errors were encountered: