Hello,
When I add this rule to my .eslintrc file Visual Studio Code triggers a popup error Cannot read property 'type' of undefined.
This is my rule:
"react/boolean-prop-naming": [1, { "rule": "(^(is|has)[A-Z]([A-Za-z0-9]?)+)|(^[a-z]+(ed|able)$)" }],
I think this is related somehow to the spread operator as the errors trigger when I type ...test
Can you show us the full piece of code that trigger the crash ? It will help us to fix the issue.
Here's a screenshot:

The error is triggered after typing ...x.
Not sure why, but if I disable the boolean rule the error stops occurring.
I can reproduce this. Will fix.
Hi, I鈥檓 running 7.4.0 and still getting this error:
package.json:
"eslint-plugin-react": "^7.4.0"
eslint is 4.7.2
.eslintrc.js:
"react/boolean-prop-naming": [
"error",
{ "rule": "^(is|has)[A-Z]([A-Za-z0-9]?)+" }
],
Error:
Cannot read property 'properties' of undefined
TypeError: Cannot read property 'properties' of undefined
at EventEmitter.MemberExpression (/Users/user/repos/myrepo/node_modules/eslint-plugin-react/lib/rules/boolean-prop-naming.js:183:45)
at emitOne (events.js:120:20)
at EventEmitter.emit (events.js:210:7)
at NodeEventGenerator.applySelector (/Users/user/repos/myrepo/node_modules/eslint/lib/util/node-event-generator.js:265:26)
at NodeEventGenerator.applySelectors (/Users/user/repos/myrepo/node_modules/eslint/lib/util/node-event-generator.js:294:22)
at NodeEventGenerator.enterNode (/Users/user/repos/myrepo/node_modules/eslint/lib/util/node-event-generator.js:308:14)
at CodePathAnalyzer.enterNode (/Users/user/repos/myrepo/node_modules/eslint/lib/code-path-analysis/code-path-analyzer.js:606:23)
at Traverser.enter (/Users/user/repos/myrepo/node_modules/eslint/lib/linter.js:962:32)
at Traverser.__execute (/Users/user/repos/myrepo/node_modules/estraverse/estraverse.js:397:31)
at Traverser.traverse (/Users/user/repos/myrepo/node_modules/estraverse/estraverse.js:501:28)
@setek please file a new issue, and ideally include the code it's crashing on :-)
Most helpful comment
@setek please file a new issue, and ideally include the code it's crashing on :-)