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
The FILE breaking change level prevents moving across files, which deals with languages where types are imported on a per-file basis. For example, in C++, if your source code imports "specific.pb.h", moving the enum to common.proto means that the type will now be in "common.pb.h", potentially resulting in compile errors for source code that doesn't import "common.pb.h". Some languages may have their header files themselves import "common.pb.h", but the FILE level aims to be as strict as possible, as we can't assume how individual language generators work. You may want to reduce your breaking change category to PACKAGE, see https://buf.build/docs/breaking/rules#categories for more details.
Before (syntax and package declarations omitted):
common.proto:
specific.proto:
After:
common.proto:
specific.proto:
We got
This seems unnecessary as the resulting effective set of available types is the same, or are we missing something?
The text was updated successfully, but these errors were encountered: