Patrice Chalin
Patrice Chalin
In particular, ensure that the quick start pages conform to the current (implicit) "template".
- Consider generating the button list from a data file, esp. since the order is currently based on top-hits. - Followup to #324, #325
(This isn't an issue with the grpc.io repo, but this seems like a convenient enough place to document the problem.) It would seem that the gRPC-Web name used to designate...
Originally from @waldyrious via https://github.com/grpc/grpc.io/pull/184#issue-402783066 > Use a semicolon instead of an empty options list. > > This is consistent with the style guide and examples and in the protobuf...
At least a subset of the redirects should be tested. I've been quite successful in writing such tests using `linkcheck`. [Releases, as of 2.0.12, have binaries that can be downloaded...
Contributes to #180 Context https://github.com/grpc/grpc-web/pull/843#issue-428746458: > We should consider the migration to grpc.io of the [quick start][] and [tutorial][] that are local to this repo, as well as parts of...
Here is what the [Guides](https://grpc.io/docs/guides) page currently looks like: > 
Originally reported for the Node tutorial via #159: > 
(AI from gRPC Docs Working Group 03/30) This is also partly in followup to @ejona86's https://github.com/grpc/grpc.io/issues/103#issuecomment-603539833: > ... some Google-internal documentation for this sort of thing ... be really happy...
Several pages contain the following text (emphasis mine): > With gRPC we can define our service once in a .proto file and implement clients and servers in any of gRPC's...