-
Notifications
You must be signed in to change notification settings - Fork 4
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
Creating .proto
definition subdomains.
#279
Labels
Comments
tegefaulkes
changed the title
- Prototype by abstracting into subdirectories under
Creating Oct 29, 2021
src/proto/schemas
, and integrate google's protobuf library by first referencing it and then just copying verbatim.proto
definition subdomains.
tegefaulkes
added a commit
that referenced
this issue
Oct 29, 2021
…t for `google.protobuf` message types. Fixes (#279)
tegefaulkes
added a commit
that referenced
this issue
Oct 29, 2021
…t for `google.protobuf` message types. Fixes (#279)
19 tasks
Remember to assign yourself here and put it in right column too. Also I think tick boxes for issues should only relate to the issue, other items go to the PR. |
CMCDragonkai
added
epic
Big issue with multiple subissues
development
Standard development
labels
Nov 1, 2021
Also I noticed this issue didn't have the labels automatically applied. Did you create the issue on github? |
I think I created it from a task list in the related issue. |
Yea if aren't directly creating issues, make sure to add the appropriate labels and metadata. |
CMCDragonkai
pushed a commit
that referenced
this issue
Nov 1, 2021
…t for `google.protobuf` message types. Fixes (#279)
CMCDragonkai
pushed a commit
that referenced
this issue
Nov 1, 2021
…t for `google.protobuf` message types. Fixes (#279)
CMCDragonkai
pushed a commit
that referenced
this issue
Nov 1, 2021
…t for `google.protobuf` message types. Fixes (#279)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Specification
We need to update the protobuf definitions to split up messages for each domain into its own domain
.proto
file. we can use package names and imports to achieve this.Additional context
Relates to #249
Tasks
The text was updated successfully, but these errors were encountered: