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.

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

chore: Add named-use-effect custom eslint rule #36725

Merged
merged 2 commits into from
Oct 9, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions app/client/packages/eslint-plugin/src/index.ts
Original file line number Diff line number Diff line change
@@ -1,13 +1,16 @@
import { objectKeysRule } from "./object-keys/rule";
import { namedUseEffectRule } from "./named-use-effect/rule";
hetunandu marked this conversation as resolved.
Show resolved Hide resolved

const plugin = {
rules: {
"object-keys": objectKeysRule,
"named-use-effect": namedUseEffectRule,
},
configs: {
recommended: {
rules: {
"@appsmith/object-keys": "warn",
"@appsmith/named-use-effect": "warn",
},
},
},
Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
import { TSESLint } from "@typescript-eslint/utils";
import { namedUseEffectRule } from "./rule";

const ruleTester = new TSESLint.RuleTester();

ruleTester.run("named-use-effect", namedUseEffectRule, {
valid: [
{
code: "useEffect(function add(){ }, [])",
},
{
code: "React.useEffect(function add(){ }, [])",
},
],
invalid: [
{
code: "useEffect(function (){ }, [])",
errors: [{ messageId: "useNamedUseEffect" }],
},
{
code: "React.useEffect(function (){ }, [])",
errors: [{ messageId: "useNamedUseEffect" }],
},
],
});
65 changes: 65 additions & 0 deletions app/client/packages/eslint-plugin/src/named-use-effect/rule.ts
Original file line number Diff line number Diff line change
@@ -0,0 +1,65 @@
import type { TSESLint } from "@typescript-eslint/utils";

export const namedUseEffectRule: TSESLint.RuleModule<"useNamedUseEffect"> = {
defaultOptions: [],
meta: {
type: "suggestion",
docs: {
description: "Warns when useEffect hook has an anonymous function",
recommended: "warn",
},
schema: [], // No options
messages: {
useNamedUseEffect:
"The function inside the useEffect should be named for better readability eg: useEffect(function mySideEffect() {...}, [])",
},
},
create(context) {
return {
CallExpression(node) {
// useEffect used directly
// eg
// import { useEffect } from "react";
// ...
// useEffect(() => {}, [])
const isDirectCall =
node.callee.type === "Identifier" && node.callee.name === "useEffect";

// useEffect used via React object
// eg
// import React from "react";
// ...
// React.useEffect(() => {}, [])
const isMemberExpressionCall =
node.callee.type === "MemberExpression" &&
node.callee.object.type === "Identifier" &&
node.callee.object.name === "React" &&
node.callee.property.type === "Identifier" &&
node.callee.property.name === "useEffect";

if (isDirectCall || isMemberExpressionCall) {
// Get the first argument which should be a function
const callbackArg = node.arguments[0];

// Arrow function are never named so it is discouraged
if (callbackArg.type === "ArrowFunctionExpression") {
context.report({
node: callbackArg,
messageId: "useNamedUseEffect",
});
}

// Function Expressions can be unnamed. This is also discouraged
if (callbackArg.type === "FunctionExpression") {
if (!callbackArg.id) {
context.report({
node: callbackArg,
messageId: "useNamedUseEffect",
});
}
}
}
},
};
},
};
Loading