metastore
metastore copied to clipboard
anemos-io
A protobuf schema registry on steroids. It will keep track of the contracts throughout your organization, making sure no contract is broken.
Metastore should not store the protobuf native descriptors, as they are handled internally.
Now, when invoking diffOnMessage or diffOnFileName multiple times, multiple entries are added to the Results report, which can lead to duplicate fields/options in the end proto when applying the report
Both message option are symaticly the same, but the `ProtoLanguageFileWriter` is unable to write the first version out (they have a different binary representation). ``` message Message { option (package.field).version...
Currently the page iteration doesn't work. Listing resource just will dump them all.
Unused import A proto file SHOULD not import another proto file without using references.
Contract leakage - Version scope It MUST always be an error when an other version of the same package is referenced.
Contract leakage - Package scope In general messages and services should only reference messages from its own package. A lint rule should be configurable to not import other packages except...
Directory and package alignment The package name and the directory should align (example package foo.bar should live in the directory foo/bar/).
Multiple fields into a new oneof May be safe if you are sure that no code sets more than one at a time. Moving any fields into an existing oneof...
Single field moved to new oneof Is safe and binary compatible. Default submit and validate behaviour is warning. As in some storage backend this field changes from required to nullable...