Lines Matching +full:json +full:- +full:schema +full:- +full:traverse
4 …ld Status](https://travis-ci.org/protocolbuffers/protobuf-go.svg?branch=master)](https://travis-ci…
8 language-neutral, platform-neutral, extensible mechanism for serializing
10 schema for structured data. This schema is compiled into language specific
20 [`protoc-gen-go`](https://pkg.go.dev/google.golang.org/protobuf/cmd/protoc-gen-go)
23 …[generate Go specific code for a given `.proto` file](https://protobuf.dev/reference/go/go-generat…
32 [JSON](https://pkg.go.dev/google.golang.org/protobuf/encoding/protojson),
37 [developer guide for protocol buffers in Go](https://protobuf.dev/getting-started/gotutorial)
55 Package `protojson` serializes protobuf messages as JSON.
59 Package `protowire` parses and formats the low-level raw wire encoding. Most
75 Package `protorange` provides functionality to traverse a protobuf message.
123 * [`cmd/protoc-gen-go`](https://pkg.go.dev/google.golang.org/protobuf/cmd/protoc-gen-go):
124 The `protoc-gen-go` binary is a protoc plugin to generate a Go protocol
137 [Go protocol buffer module](https://github.com/protocolbuffers/protobuf-go/releases)
144 This project is open-source and accepts contributions. See the
145 [contribution guide](https://github.com/protocolbuffers/protobuf-go/blob/master/CONTRIBUTING.md)
171 by `protoc-gen-go`. Such practice is not supported by this project.
174 …[`protoc-gen-go/internal_gengo`](https://pkg.go.dev/google.golang.org/protobuf/cmd/protoc-gen-go/i…
184 [`protoc-gen-go`](https://pkg.go.dev/google.golang.org/protobuf/cmd/protoc-gen-go)
199 ([released in 2020](https://blog.golang.org/a-new-go-api-for-protocol-buffers))
203 ([released publicly in 2010](https://blog.golang.org/third-party-libraries-goprotobuf-and))
219 // 2007/09/25 - Conception of Go
245 // 2012/03/28 - Release of Go 1
255 The change on June 6th, 2012 added a degree of type-safety to Go protobufs by
280 `protoc-gen-go`. Since `protoc-gen-go` would always generate messages with the
289 `protoc-gen-go`.
295 message implementation might work with some top-level functions (e.g.,
303 write general-purpose code that operates on any protobuf message. For
308 `protoc-gen-go`). If the concrete message type did not match this