no-memo-children

errorSuggestionType-aware

Reports memo(...) calls when the component props type includes a children property.

Rule details Suggestion

The rule checks imported memo calls from react or @rbxts/react, based on the configured environment. If the memoized component’s props type has a children property, it reports the call.

It resolves children through direct props, inherited interfaces, intersections, and unions. You can also allow specific component names with allowedComponents.

Examples

Incorrect

Memoized component with children

import { memo, ReactNode } from "@rbxts/react";

interface CardProps {
  readonly title: string;
  readonly children?: ReactNode;
}

const Card = memo<CardProps>((props) => {
  return <frame>{props.children}</frame>;
});

Correct

Component without children

import { memo } from "@rbxts/react";

interface ButtonProps {
  readonly label: string;
}

const Button = memo<ButtonProps>((props) => {
  return <textbutton Text={props.label} />;
});

Options

Option	Type	Default	Notes
`allowedComponents`	`string[]`	`[]`	Component names the rule should skip.
`environment`	`"roblox-ts" \| "standard"`	`"roblox-ts"`	Picks `@rbxts/react` or `react` imports.

import ceaseNonsense from "@pobammer-ts/eslint-cease-nonsense-rules";

export default [
  {
    plugins: {
      "cease-nonsense": ceaseNonsense,
    },
    rules: {
      "cease-nonsense/no-memo-children": [
        "error",
        {
          allowedComponents: ["PortalHost"],
          environment: "standard",
        },
      ],
    },
  },
];

no-new-instance-in-use-memoKeeps useMemo callbacks free of object construction

require-react-display-namesRequires display names for React components