What is eslint-plugin-functional?
eslint-plugin-functional is an ESLint plugin that enforces functional programming best practices. It helps developers write code that is more predictable, easier to test, and less prone to bugs by discouraging side effects, mutable data, and other non-functional programming patterns.
What are eslint-plugin-functional's main functionalities?
No Mutations
This feature enforces immutability by disallowing the use of `let`, `this`, and `class`. This ensures that variables and data structures remain constant throughout the code.
module.exports = {
rules: {
'functional/no-let': 'error',
'functional/no-this-expression': 'error',
'functional/no-class': 'error'
}
};
No Expressions with Side Effects
This feature prevents the use of expressions that produce side effects, such as assignments and conditionals. This helps in maintaining pure functions that are easier to test and reason about.
module.exports = {
rules: {
'functional/no-expression-statement': 'error',
'functional/no-conditional-statement': 'error'
}
};
No Loops
This feature disallows the use of loop statements like `for`, `while`, and `do-while`. Instead, it encourages the use of higher-order functions like `map`, `filter`, and `reduce` for iteration.
module.exports = {
rules: {
'functional/no-loop-statement': 'error'
}
};
Other packages similar to eslint-plugin-functional
eslint-plugin-immutable
eslint-plugin-immutable is an ESLint plugin that enforces immutability rules in JavaScript code. It is similar to eslint-plugin-functional in that it discourages the use of mutable data structures and promotes the use of immutable patterns. However, it is more focused on immutability rather than a broader range of functional programming principles.
eslint-plugin-fp
eslint-plugin-fp is an ESLint plugin that enforces functional programming best practices. It is similar to eslint-plugin-functional but has a different set of rules and focuses more on preventing side effects and promoting pure functions. It also includes rules for avoiding certain JavaScript features that are considered non-functional.
eslint-plugin-no-loops
eslint-plugin-no-loops is an ESLint plugin that disallows the use of loop statements in JavaScript code. It is similar to the 'No Loops' feature of eslint-plugin-functional but is more specialized, focusing solely on preventing loops and encouraging the use of higher-order functions for iteration.
Donate
Any donations would be much appreciated. π
Enterprise Users
eslint-plugin-functional
is available as part of the Tidelift Subscription.
Tidelift is working with the maintainers of eslint-plugin-functional
and a growing network of open source maintainers to ensure your open source software supply chain meets enterprise standards now and into the future.
Learn more.
Getting Started
See our getting started guide.
Rulesets
The following rulesets are made available by this plugin.
Presets:
-
Strict (plugin:functional/strict
)
Enforce recommended rules designed to strictly enforce functional programming.
-
Recommended (plugin:functional/recommended
)
Has the same goal as the strict
preset but a little more lenient, allowing for functional-like coding styles and nicer integration with non-functional 3rd-party libraries.
-
Lite (plugin:functional/lite
)
Good if you're new to functional programming or are converting a large codebase.
Categorized:
-
Currying (plugin:functional/currying
)
JavaScript functions support syntax that is not compatible with curried functions. To enforce currying, this syntax should be prevented.
-
No Exceptions (plugin:functional/no-exceptions
)
Functional programming style does not use run-time exceptions. Instead expressions produces values to indicate errors.
-
No Mutations (plugin:functional/no-mutations
)
Prevent mutating any data as that's not functional
-
No Other Paradigms (plugin:functional/no-other-paradigms
)
JavaScript is multi-paradigm, allowing not only functional, but object-oriented as well as other programming styles. To promote a functional style, prevent the use of other paradigm styles.
-
No Statements (plugin:functional/no-statements
)
In functional programming everything is an expression that produces a value. JavaScript has a lot of syntax that is just statements that does not produce a value. That syntax has to be prevented to promote a functional style.
-
Stylistic (plugin:functional/stylistic
)
Enforce code styles that can be considered to be more functional.
Other:
-
All (plugin:functional/all
)
Enables all rules defined in this plugin.
-
Off (plugin:functional/off
)
Disable all rules defined in this plugin.
-
Disable Type Checked (plugin:functional/disable-type-checked
)
Disable all rules that require type information.
-
External Vanilla Recommended (plugin:functional/external-vanilla-recommended
)
Configures recommended vanilla ESLint rules.
-
External Typescript Recommended (plugin:functional/external-typescript-recommended
)
Configures recommended TypeScript ESLint rules.
Enabling this ruleset will also enable the vanilla one.
The below section gives details on which rules are enabled by each ruleset.
Rules
πΌ Configurations enabled in.
β οΈ Configurations set to warn in.
π« Configurations disabled in.
βοΈ Set in the lite
configuration.
β
Set in the recommended
configuration.
π Set in the strict
configuration.
π¨ Set in the stylistic
configuration.
π§ Automatically fixable by the --fix
CLI option.
π‘ Manually fixable by editor suggestions.
π Requires type information.
β Deprecated.
Currying
Name | Description | πΌ | β οΈ | π« | π§ | π‘ | π | β |
---|
functional-parameters | Enforce functional parameters. | βοΈ β
π | | | | | | |
No Exceptions
No Mutations
NameΒ Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β | Description | πΌ | β οΈ | π« | π§ | π‘ | π | β |
---|
immutable-data | Enforce treating data as immutable. | βοΈ β
π | | | | | π | |
no-let | Disallow mutable variables. | βοΈ β
π | | | | | | |
prefer-immutable-types | Require function parameters to be typed as certain immutability | βοΈ β
π | | | π§ | π‘ | π | |
prefer-readonly-type | Prefer readonly types over mutable types. | | | | π§ | | π | β |
type-declaration-immutability | Enforce the immutability of types based on patterns. | βοΈ β
π | | | π§ | | π | |
No Other Paradigms
NameΒ Β Β Β Β Β Β Β Β Β Β Β Β Β Β | Description | πΌ | β οΈ | π« | π§ | π‘ | π | β |
---|
no-classes | Disallow classes. | βοΈ β
π | | | | | | |
no-mixed-types | Restrict types so that only members of the same kind are allowed in them. | βοΈ β
π | | | | | π | |
no-this-expressions | Disallow this access. | π | | βοΈ β
| | | | |
No Statements
Stylistic
NameΒ Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β | Description | πΌ | β οΈ | π« | π§ | π‘ | π | β |
---|
prefer-property-signatures | Prefer property signatures over method signatures. | π¨ | | | | | π | |
prefer-tacit | Replaces x => f(x) with just f . | | π¨ | | | π‘ | π | |
readonly-type | Require consistently using either readonly keywords or Readonly<T> | π¨ | | | π§ | | π | |
External Recommended Rules
In addition to the above rules, there are a few other rules we recommended.
These rules are what are included in the external recommended rulesets.
Vanilla Rules
-
no-var
Without this rule, it is still possible to create mutable var
variables.
-
no-param-reassign
Don't allow function parameters to be reassigned, they should be treated as constants.
-
prefer-const
This rule provides a helpful fixer when converting from an imperative code style to a functional one.
Typescript Rules
Contributing
See our contributing guide.
Prior work
This project started as a port of tslint-immutable
which was originally inspired by eslint-plugin-immutable.