← Back to rules

react/no-this-in-sfc Correctness

What it does

Prevents using this in stateless functional components.

Why is this bad?

In React, stateless functional components (SFCs) receive props and context as function parameters, not through this. Using this in an SFC typically indicates a mistake when converting from class components or unfamiliarity with the two component styles.

Examples

Examples of incorrect code for this rule:

function Foo(props) {
  return <div>{this.props.bar}</div>;
}

function Foo(props) {
  const { bar } = this.props;
  return <div>{bar}</div>;
}

const Foo = (props) => (this.props.foo ? <span>{props.bar}</span> : null);

Examples of correct code for this rule:

function Foo(props) {
  return <div>{props.bar}</div>;
}

function Foo({ bar }) {
  return <div>{bar}</div>;
}

class Foo extends React.Component {
  render() {
    return <div>{this.props.bar}</div>;
  }
}

How to use

To enable this rule using the config file or in the CLI, you can use:

Config (.oxlintrc.json)

{
  "plugins": ["react"],
  "rules": {
    "react/no-this-in-sfc": "error"
  }
}

Config (oxlint.config.ts)

import { defineConfig } from "oxlint";

export default defineConfig({
  plugins: ["react"],
  rules: {
    "react/no-this-in-sfc": "error",
  },
});

CLI

oxlint --deny react/no-this-in-sfc --react-plugin

Version

This rule was added in v1.37.0.

References

• Rule Source
• Upstream rule docs
• Open rule in Oxc Playground