Joshua Humphries
Joshua Humphries
A previously merged fix (#169) addressed the file path matching problem for loading linked-in local registered files (#147). It turns out, the same sort of thing is needed for remote...
This is a case where protoparse accepts a proto source file that protoc rejects. When a file uses `syntax = "proto3"`, protoc _requires_ that all fields have unique JSON names....
The representation of gRPC requests and message data on the wire in the `httpgrpc` package is quite different from that used to by `grpc-web` (which also aims to support gRPC...
gRPC can support non-protobuf messages via custom codecs. It can also support protobuf messages while using a different on-the-wire representation via custom codecs (such as using JSON on the wire)....
This syntax is supported by protoc so should also be supported by goprotoc.
There were a few bugs in the formatter that were uncovered with the new version of `protocompile`, mostly around trailing vs. leading comments. For example, there was previously a bug...
Fixes #6335 -- just the validation of strings part, not the ambiguity issues (which likely calls for a separate issue since it really requires a minor language change).
This makes a few other related changes, for consistency: * Adds the existing checks, for default JSON names, to run even for proto2 files, but only as warnings (symmetry with...
This is a re-do of #10581. Merging this PR previously caused issues when importing the change into Google's internal repo (IIUC). So additional testing is needed before attempting to merge...