Open kinland opened 1 year ago
Thank you @kinland. I have been busy on other projects for a while, so I can't remember the details of the module that parses the config... but This may have something to do with the spreading of the array. You can verify this by moving the contents of the array directly into the config options.
In my
.eslintrc.js
, I have:This is then used in a rule like so:
'@typescript-eslint/naming-convention': ['error', ...namingConventionRules],
This causes an
options[0] must be object
error:I thought, "maybe it's not realizing those are objects, so if I make it explicit, it'll work, so I tried this slight change to my code:
No dice: