You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am locally testing my protobuf file using this linter and it's throwing below errors. Can you help me to resolve the issue?
My protobuf file is in the protoc-gen-lint-master folder.
C:\Repo\protoc-gen-lint-master>protoc --lint_out=. *.proto
'protoc-gen-lint' is not recognized as an internal or external command,
operable program or batch file.
--lint_out: protoc-gen-lint: Plugin failed with status code 1.
I have also tested my proto file with the google style guide rules. I didn't see any of the naming convention rules are executed by this linter. which is not giving any expected errors or suggestions. Can you share more information on it?
Thank you!
The text was updated successfully, but these errors were encountered:
I have figured out the above issues and got working locally protoc-gen-lint. I have tested my protobuf files against google style guide and found below test cases are not passing by this linter.
TEST Cases Failed:
Files should be named lower_snake_case.proto (I have given UPPERCASE_NAME.proto and it's not throwing any error!)
Package name should be in lowercase (I have given UPPERCASEPACKAGENAME and it's not throwing any error!)
Repeated fields -> Use pluralized names for repeated fields (I have given a singular name and it's not throwing any error!)
Can you please give any suggestions on these test cases?
Hello @ckaznocha,
I am locally testing my protobuf file using this linter and it's throwing below errors. Can you help me to resolve the issue?
My protobuf file is in the
protoc-gen-lint-master
folder.I have also tested my proto file with the google style guide rules. I didn't see any of the naming convention rules are executed by this linter. which is not giving any expected errors or suggestions. Can you share more information on it?
Thank you!
The text was updated successfully, but these errors were encountered: