This repo contains common protobuf definitions intended to be shared to other repos as a submodule. So far, the dependent repos are:

• blueinternal
• blueapi

Since there is no build system here, correctness can only be resolved through the importer's build system. It is assumed that the importing repo can resolve the imports used. For example, entity.proto imports struct.proto like so:

import "google/protobuf/struct.proto";

This assumes that your repo should be able to resolve google/protobuf/struct.proto locally during compilation.

Another caveat is the go_package definition. As of this writing, I (@flowerinthenight) don't know of any way to unify the definition across multiple repos. For example, if imported to blueinternal, it needs to be defined as:

import "github.com/alphauslabs/blue-internal-go/protos"

while in blueapi, it should be:

import "github.com/alphauslabs/blue-sdk-go/protos"

Please update the build system when you figure it out. At the moment, this is handled by updating import lines using sed. As a stopgap solution, when adding a new proto definition, define your go_package like so:

option go_package = "github.com/alphauslabs/tobereplaced";

This will be fixed and finalized by the importer's build system. As long as your package ***; definition is correct, you should be able to build locally.