protocol-buffers
Here are 482 public repositories matching this topic...
Is there a document anywhere that describes how to upgrade a v1 project to a v2 project? There is a blog post, however it isn't comprehensive. I tried searching both in this repository and in https://github.com/protocolbuffers/protobuf-go.
Currently, I'm running into this error, and I'm unsure how to resolve it. (I can open this specific instance as a separate issue. However, were an upgrade gu
Hey in the documentation:
https://protobufjs.github.io/protobuf.js/
the Buffer class is 404:
https://protobufjs.github.io/protobuf.js/Buffer.html
though it is being linked to in some other classes, e.g. BufferReader
https://protobufjs.github.io/protobuf.js/BufferReader.html
kind regards
I have a module with two proto files in a directory. File1 is under directory dir1 and File2 is under dir2. Both dir1 and dir2 are under dir0.
I have the below configuration for the "doc" plugin.
- name: doc
flags: markdown,test.md
output: docs
when I invoke prototool by passing dir0 as input, I see it protoc command twice (once for each proto file). This cause
Where's the instructions to convert interface type to protobuf and reverse it?
Can you put on the front page of this project? Where's the tutorial link?
-
Updated
Jul 2, 2020 - Swift
-
Updated
Jul 2, 2020
I added custom build step to my build system that regenerates .c and .h files for my .proto file.
Unfortunately, nanopb puts this comment with current time and date in them :
/* Automatically generated nanopb constant definitions */
/* Generated by nanopb-0.3.9 at Mon Mar 26 19:15:47 2018. */
That makes git sad because files change on every build.
Is it possible to stop this comme
-
Updated
Jun 27, 2020 - Go
Similar to #537, we should allows users to have more flexibility in how they send messages. At the moment they only have:
sendResponse(message:) -> EventLoopFuture<Void>
Ideally there should be options to:
- provide an optional promise
- choose whether to flush or not
- send multiple messages
- manually flush
This would bring it into alignment to the client with changes made in #538
-
Updated
May 30, 2019 - Swift
As discussed in #217, the implementation of UUID matching is sub-optimal because it uses a hard coded constant regex string passed to a regex library. Significant performance gains can be achieved by replacing constant regex expressions with bespoke state machines.
This work is worth doing because UUIDs are so common in distributed systems and PGV sits on the hot path of every service request.
This came up in #356 that device actions support in the sample is not very discoverable.
We should consider:
- move the actions.json in the
pushtotalkdirectory - add instruction to deploy the actions package in the README.md
- document the step to try both built-in and custom
Typescript warns Expected 0 arguments, but got 1. when I pass arguments for a protobuf message constructor. google-protobuf implementation of protobuf Message accept arguments.
// input.proto
message InputType {
string name = 1;
string email = 2;
}
// errors in typescript
new InputType(['my name', 'my email'])
Consider adding a constructor method to the ty
-
Updated
Jun 30, 2020 - Go
If you use gogoproto's custom types (https://github.com/gogo/protobuf/blob/master/custom_types.md) e.g.:
import "myorg/customtypes/time/time.proto";
...
message Example {
time.CustomTime created = 3 [(gogoproto.customtype) = "myorg/customtypes/time.CustomTime"];
}
mwitkow validators generates a file with unused imports:
19:33:28 generated/xxxx.pb.go:17:2: importe
-
Updated
Jun 30, 2020 - JavaScript
-
Updated
Oct 21, 2019 - Python
Please ask which one, some may be outdated or low priority.
-
Updated
Jun 30, 2020 - Go
-
Updated
May 17, 2020 - JavaScript
-
Updated
May 31, 2020 - Python
-
Updated
Jul 1, 2020 - Go
-
Updated
Jul 2, 2020 - Elixir
-
Updated
Feb 4, 2020 - Kotlin
I'm writing a Scala plugin to implement a compatibility check. For some reason I wrote the structure of the plugin input from the wiki readme rather than the code. In the process of getting it working I found some differences between the JSON structure in the readme and what is sent by protolock.
It seems I can't fork the wiki, so I'll attach a patch to this issue (apparently as a text file b
-
Updated
May 26, 2020 - Go
Improve this page
Add a description, image, and links to the protocol-buffers topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the protocol-buffers topic, visit your repo's landing page and select "manage topics."
URL: https://developers.google.com/protocol-buffers/docs/reference/cpp/google.protobuf.message
There appears to be an errant markup text in the code example at the top of the page. This is how it renders for me in Chrome 80 on Ubuntu 16.04:
