feat: implement naming-convention rule#664
Conversation
There was a problem hiding this comment.
this test structure looks quite different to the original rule - this makes it hard to review, and tricky to tell if we have complete test coverage with the original rule.
Do you mind porting the tests exactly?
Thanks
There was a problem hiding this comment.
Hi,
The ESLint test suite had a dynamic generated test suite via their helper createTestCases
https://github.com/typescript-eslint/typescript-eslint/blob/68a074fb61a10c3627f09678859fb4d42a3b88f5/packages/eslint-plugin/tests/rules/naming-convention/cases/createTestCases.ts#L87
For this I'm not sure what the right approach would be for tsgolint
As for the static tests I think I ported them all, will double check and get back to you.
There was a problem hiding this comment.
I see, let me think about it a bit more
There was a problem hiding this comment.
What's your thoughts then? Is it good? (this is just a reminder for you :) ) @camc314
There was a problem hiding this comment.
|
Thank you for addressing this! |
|
Are there any updates on this rule? |
6e4e775 to
d284015
Compare
| //go:linkname checkerCheckSourceFile github.com/microsoft/typescript-go/internal/checker.(*Checker).checkSourceFile | ||
| func checkerCheckSourceFile(recv *checker.Checker, ctx context.Context, sourceFile *ast.SourceFile) |
There was a problem hiding this comment.
note to selff: we shuoldn't be exposing stuff like this
fixes #186