Is this possible?

[frederikhors]

@stefandanaita thanks for your work.

Do you think this can help me with hyperium/tonic#1386?

[stefandanaita]

I don't think it helps given your current setup, but it would probably be a good idea to separate your contracts from the workspace members, in which case you would be able to use grpc-build to improve your ergonomics.

[frederikhors]

I don't understand what you mean.

Do yo mean to have proto dir with:

• player.proto
• team.proto
• and_so_on.proto

instead of:

• player/player.proto
• team/team.proto

?

[stefandanaita]

Hmm, not exactly. I've looked at your dir structure in the tonic issue you linked above and it looks like you have separate cargo workspaces for all your protos, including the common.proto.

I was suggesting this structure

- Cargo.toml (workspace)
- src
  - protos
    - Cargo.toml
    - build.rs
    - src
      - common.proto
      - players
        - players.proto
      - teams
        - teams.proto
  - other application code workspaces, if needed at all

If you do it this way, importing the common protos into your teams or players becomes a matter of import "<replace with package name in common.proto>/common.proto";

Unless you have a specific reason for which you need the protos to be separate into different cargo workspaces, the one workspace approach makes it much simpler and easier to iterate on.