weird issue with `react/jsx-no-bind`

this is my .eslintrc:

{
    "root": true,
    "parser": "babel-eslint",
    "extends": "airbnb",
    "ecmaFeatures": {
        "classes": true,
        "jsx": true
    },
    "plugins": [
      "react"
    ],
    "rules": {
      "react/display-name": 1,
      "react/jsx-filename-extension":0,
      "react/jsx-no-bind": 2,
      "semi": [ 2, "never" ],
      "import/no-extraneous-dependencies": 0,
      "no-use-before-define": 0,
      "no-underscore-dangle": 0,
      "import/prefer-default-export": 0,
    }
}

For some reason, the rule react/jsx-no-bind doesn’t work for me while extending airbnb. If I remove the "extends": "airbnb",, I get lint errors, but when I extend, lint ignores any setting I might have and doesn’t show errors/warning at all.

[Kufert]

"react/jsx-no-bind": [2, {}] worked for me

[edgar0011]

Sure, but why would you want to use yml for config when you have any other choice

1. you come to a project wehere yaml already is, due to many reasons
2. yaml has some advantages over json: Advantages of YAML: In YAML, there is no extra delimiter is used. So it is the lightweight than XML and JSON. YAML, not using delimiter also makes the reading light and simple. (I am not sure if you agree with this point. Because many geeks find it easier to read the data in content delimiter or tags separate those.) YAML makes the data understanding easy. So it is useful in case of configuration. YAML has a wide variety of uses and popular for. It can be used for configuration, then from transferring data to storing intermediate data. YAML is the superset of JSON. You heard it right. Whatever valid JSON code you have, it will be parsed by YAML compiler. So choosing YAML over JSON for your project you have one advantage. You can parse both JSON and YAML code with the single parser (YAML parser). source: https://www.csestack.org/advantages-disadvantages-yaml/