Arthur Zahorski
Arthur Zahorski
I'd happily accept a PR addressing the issue
@havenchyk Will appreciate a PR
Yes, seems this would require signature type aware order sorting and/or allow the rule leverage `@typescript-eslint/member-ordering`
Doesn't this do the work https://github.com/typescript-eslint/typescript-eslint/blob/master/packages/eslint-plugin/docs/rules/member-ordering.md#sorting-alphabetically-within-member-groups?
I see. Well interface member type signature could be extracted from the node. Then the rule should accept an array of types as options that are going to be used...
Hey @JoshuaKGoldberg Thanks for reaching out! There are many plugin users on npm, so I would expect all the of the options from [interface](https://github.com/infctr/eslint-plugin-typescript-sort-keys/blob/master/docs/rules/interface.md) and [string-enum](https://github.com/infctr/eslint-plugin-typescript-sort-keys/blob/master/docs/rules/string-enum.md) rules to be supported...
I can see that `requiredFirst: true` is not supported in `member-ordering`, is it?
@JoshuaKGoldberg Go ahead :)
Given the following config: ```js module.exports = { scripts: { test: { default: 'jest --config jest/config.js', }, }, } ``` Got passing arguments to work like this `yarn nps "test...
I've been able to narrow down to the line of code that causes the error message, an arrow function returning `false` seems to be the culprit. Made some other tests...