-
Notifications
You must be signed in to change notification settings - Fork 52
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
Protolint substituting "message" with " sage" #139
Comments
@navaneeth-spotnana Thank you for reporting a bug. |
I observed similar behaviour with return statements:
Are you going to take this up and fix it? Golang is not very familiar for me, I can take a stab at it otherwise. |
I was reading the code, and this is what I understand:
The above code snippet won't work in case there are more than one elements on the same line. What would be the fix for this? |
@navaneeth-spotnana Thank you for investigating this issue! What do you think about the change that protolint will do nothing against inner elements on the same line? PS. If someone wants to format a file like converting to multiple lines with correct indentation, it would be better to support a new |
👎🏽 Please don't. That's very important for me. I am considering using protolint inside our company, and if it doesn't insert proper linebreaks, it will be disappointing.
Agreed, I had the same thoughts while going through the code last week. Full rewrite might be easier than editing. |
@navaneeth-spotnana Thank you for sharing your thought. |
In a way, full rewrite might be better, as this might enable us to support file structure guidelines? |
@daltonfury42 That's right. |
@navaneeth-spotnana I fixed this issue by #141. Can you confirm v0.27.0 works for you? |
Yes it's working, thanks a lot. |
I am running
protolint version 0.26.1(84c57fd)
running onmacOS 11.0.1
, and it's making this wrong transformation:Looks like it's making a wrong transformation. To reporoduce the issue, save the below text into a .proto file:
Run:
It prints the below output to console:
The text was updated successfully, but these errors were encountered: