Initial implementation of Google API protobufs #1348
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
This is a very initial proposal to address #876. I have compiled the latest main branch of the Google's API Common Protobuf repository, as it contains all the expected Protobufs referenced in the official docs. I would love to get feedback on this. Main points I am interested in:
prost-typesinstead under a feature flag?api-common-protosrepository as it is smaller and self-contained. The latest docs point to https://github.com/googleapis/googleapis/, which is much bigger/bloated. I don't feel like we need this, but happy to change over.prost-buildand/orprostand have some sort of.with_googleapis(true)flag that also injects includes properly and setsgoogle::namespace as a separate source obtained from this crate?build.rswith selective generation of only included protos, if people feel strongly about it.Any other thoughts or ideas are appreciated!
Fixes #876