-
Notifications
You must be signed in to change notification settings - Fork 764
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
Disable static checkers on generated js files #752
Conversation
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the contributions!
@stanley-cheung happy to help! this is a very nice project ❤️ Going deeper into the causes of this issue is because the code relies on |
No plan to support ES6 modules for now because protobuf doesn't support ES6 modules yet: https://github.com/protocolbuffers/protobuf/tree/master/js#protocol-buffers---googles-data-interchange-format |
I'm still getting 'proto' is not defined (and 'COMPILED') on the protobuf JS file. Do you think the protocolbuffers/protobuf project would add these lines to the protobuf JS file? |
I can confirm this has only been added to the |
I was getting TypeScript errors on the generated protobuf file. These directives to turn off ESLint and TypeScript are just comments. They shouldn't affect anyone who is not using ESLint or TypeScript. A similar change was made in the grpc/grpc-web project: grpc/grpc-web#752
I was getting TypeScript errors on the generated protobuf file. These directives to turn off ESLint and TypeScript are just comments. They shouldn't affect anyone who is not using ESLint or TypeScript. A similar change was made in the grpc/grpc-web project: grpc/grpc-web#752
I was getting TypeScript errors on the generated protobuf file. These directives to turn off ESLint and TypeScript are just comments. They shouldn't affect anyone who is not using ESLint or TypeScript. A similar change was made in the grpc/grpc-web project: grpc/grpc-web#752
This will work as a hotfix for #447
I think it could make sense to include it.
Since those are auto generated they never should be edited so it would be ok disable static checkers.
Eslint:
https://eslint.org/docs/2.13.1/user-guide/configuring#disabling-rules-with-inline-comments
Typescript
https://www.typescriptlang.org/docs/handbook/type-checking-javascript-files.html