yohei yoshimuta

@PaulSonOfLars Good catch on the case! It's not intended. I just missed that case. [memo] ref. Implementation - https://github.com/yoheimuta/protolint/blob/9364a237a4396a9ca583f0543da4df40d51343d8/internal/addon/rules/indentRule.go

@ayedo Glad to hear that! I'm afraid there is not a rule to detect spaces between the name and the semicolon. But, the rule sounds helpful.

@PaulSonOfLars Thank you for your excellent suggestion! At first glance, I agree with that. > A stretch goal and dream for me would also be if you allowed multiple output...

@DoneSpeak > Maybe I have figured out the reason. That's right. > I think it should be a verify error like the following content instead of a code error which...

Thank you for clarifying the issue. Handling UTF-8 BOM (U+FEFF) properly seems worth it. Whenever I have time, I'm getting to it.

@tzachshabtay Thank you for your suggestion. It sounds useful. I attached the label to this issue for starters.

@dtaniwaki Thank you for your nice feedback! It sounds useful. I attached the label to this issue for now.

@alexhayes Thank you for reaching out. > I discovered that oneof fields are not linted by the rule Oneof fields are `string eggs = 1;` and `string sausage = 2;,`...

@WinBeyond Currently, go-protoparser doesn't have the feature. Theoretically, it's possible to implement the feature reverting from JSON conforming Proto type.

@wirekang No, FieldNumber must be a number, according to [the spec](https://developers.google.com/protocol-buffers/docs/reference/proto3-spec#fields). Practically, [Go's int type](https://go.dev/ref/spec#Integer_literals) can cover [the sensible FieldNumber value](https://developers.google.com/protocol-buffers/docs/reference/proto2-spec#integer_literals). However, each size limit is different. Let's say users...