-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conflict to @typescript-eslint/member-ordering #30
Comments
Yes, seems this would require signature type aware order sorting and/or allow the rule leverage |
Any hints on how should i did the code change ? i can help for open PR for that |
Unfortunately it didn't have autofix feature :( |
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 for sorting just the way |
Would be nice to have this resolved, facing the same issue. |
There is a way to ignore methods and only sort keys? In the meantime, a workaround is to move all methods to a separated interface and extend it, so they are sorted separately. 😅 |
@infctr seems like @nelson6e65 landed on the right fix here. what's the chance of getting this fixed? |
I like this plugin idea which will auto-fix the member ordering inside interface
but seem it would conflict to
member-order
because this plugin don't care the member type
E.G. given below interface
it would complain error in above interface because a is after b.
But if fix it by move a before b,
member-ordering
would complain method should after attribute.Beside turn off either one, did it any suggestion can keep both running ?
The text was updated successfully, but these errors were encountered: