dimitrovvlado / proto-lint-maven-plugin Goto Github PK

A common practice is to have imports alphabetically ordered. It might be useful to have a validator to enforce that.

With the current release (1.0.1), nested messages are not being validated. Consider the following snippet:

message SampleMessage {
    message SampleNestedMessage {
        int32 sampleField = 1;
    }
}

The sampleField field is invalid, because it's not in lower underscore case.

Compatibility checker should validate whether a new version of a proto file introduces incompatible changes. A valid approach will probably execute a git diff against each proto file.

This validator should be disabled by default.

The first enum value must be zero in proto3.