-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is this possible? #38
Comments
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 |
I don't understand what you mean. Do yo mean to have
instead of:
? |
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 I was suggesting this structure
If you do it this way, importing the common protos into your teams or players becomes a matter of 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. |
@stefandanaita thanks for your work.
Do you think this can help me with hyperium/tonic#1386?
The text was updated successfully, but these errors were encountered: