When using protoc, it's often common to include . as an include path. What this means is that proto files can import other files that are in the same directory as them. This also seems to be the default behaviour when using buf.build
The current workaround is to define the proto include path to include the folder where your protos are. The issue with this approach is that sometimes proto filenames are fairly generic like "enums.proto", so if you have multiple directories with proto files in your project this all falls apart.
Allowing a tickbox for relative imports would fix this.
When using protoc, it's often common to include . as an include path. What this means is that proto files can import other files that are in the same directory as them. This also seems to be the default behaviour when using buf.build
The current workaround is to define the proto include path to include the folder where your protos are. The issue with this approach is that sometimes proto filenames are fairly generic like "enums.proto", so if you have multiple directories with proto files in your project this all falls apart.
Allowing a tickbox for relative imports would fix this.