Skip to content
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

Next steps on proto/grpc documentation #29

Closed
1 of 4 tasks
alexeagle opened this issue Feb 16, 2022 · 1 comment
Closed
1 of 4 tasks

Next steps on proto/grpc documentation #29

alexeagle opened this issue Feb 16, 2022 · 1 comment
Labels
help wanted Extra attention is needed

Comments

@alexeagle
Copy link
Contributor

alexeagle commented Feb 16, 2022

#28 (comment) lists:

  • A gazelle -> proto_library section would be useful following from the discussion above, but I don't think I'm well placed to write it, as I generally don't have enough experience with Gazelle. So yeah, I'll leave that open to anyone that feels they know it well.
    "Toolchains, how to use a prebuilt protoc." This is semi covered in the issues section discussing caching
  • "Relevant bazel flags and explanations." There only seem to be a few documented proto relevant flags remaining nowadays, of which the only one I've still seen used is the experimental --experimental_proto_descriptor_sets_include_source_info when using documentation plugins.
  • You probably want to fixup the index page for the GH pages site. Something like what the SIG is, who's sponsoring it, what it's funding etc.
  • "Relationship of FileDescriptorSet with proto_library and descriptor_set_in." This'd probably fit in a section on 'Implementing a Ruleset', which is a book all of its own.
@alexeagle alexeagle added help wanted Extra attention is needed community labels Mar 21, 2022
@alexeagle
Copy link
Contributor Author

Broken out to
#31
#32
#33

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant