Chiebot-Mirror
/
protobuf
mirror of https://github.com/protocolbuffers/protobuf.git
8
0
Fork 0
Code Issues Projects Releases Wiki Activity
Protocol Buffers - Google's data interchange format (grpc依赖) https://developers.google.com/protocol-buffers/
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
12164 Commits
201 Branches
346 Tags
254 MiB
Tag: Branch: Tree: 906e031592
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '906e031592'
${ noResults }
protobuf/docs/options.md

484 lines
10 KiB
Raw Normal View History Unescape

Auxillary -> Auxiliary
5 years ago
# Protobuf Global Extension Registry
This file contains a global registry of known extensions for descriptor.proto,
so that any developer who wishes to use multiple 3rd party projects, each with
their own extensions, can be confident that there won't be collisions in
extension numbers.
If you need an extension number for your custom option (see [custom options](
https://developers.google.com/protocol-buffers/docs/proto#customoptions)),
please [send us a pull request](https://github.com/protocolbuffers/protobuf/pulls) to
add an entry to this doc, or [create an issue](https://github.com/protocolbuffers/protobuf/issues)
with info about your project (name and website) so we can add an entry for you.
## Existing Registered Extensions
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
1. C# port of protocol buffers
Auxillary -> Auxiliary
5 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
* Website: https://github.com/jskeet/protobuf-csharp-port
* Extensions: 1000
Auxillary -> Auxiliary
5 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
1. Perl/XS port of protocol buffers
Auxillary -> Auxiliary
5 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
* Website: http://code.google.com/p/protobuf-perlxs
* Extensions: 1001
Auxillary -> Auxiliary
5 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
1. Objective-C port of protocol buffers
Auxillary -> Auxiliary
5 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
* Website: http://code.google.com/p/protobuf-objc
* Extensions: 1002
Auxillary -> Auxiliary
5 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
1. Google Wave Federation Protocol open-source release (FedOne)
Auxillary -> Auxiliary
5 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
* Website: http://code.google.com/p/wave-protocol
* Extensions: 1003
Auxillary -> Auxiliary
5 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
1. PHP code generator plugin
Auxillary -> Auxiliary
5 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
* Website: ???
* Extensions: 1004
Auxillary -> Auxiliary
5 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
1. GWT code generator plugin (third-party!)
Auxillary -> Auxiliary
5 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
* Website: http://code.google.com/p/protobuf-gwt/
* Extensions: 1005
Auxillary -> Auxiliary
5 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
1. Unix Domain RPC code generator plugin
Auxillary -> Auxiliary
5 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
* Website: http://go/udrpc
* Extensions: 1006
Auxillary -> Auxiliary
5 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
1. Object-C generator plugin (Plausible Labs)
Auxillary -> Auxiliary
5 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
* Website: http://www.plausible.coop
* Extensions: 1007
Auxillary -> Auxiliary
5 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
1. TBD (code42.com)
Auxillary -> Auxiliary
5 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
* Website: ???
* Extensions: 1008
Auxillary -> Auxiliary
5 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
1. Goby Underwater Autonomy Project
Auxillary -> Auxiliary
5 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
* Website: https://github.com/GobySoft/goby
* Extensions: 1009
Auxillary -> Auxiliary
5 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
1. Nanopb
Auxillary -> Auxiliary
5 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
* Website: http://kapsi.fi/~jpa/nanopb
* Extensions: 1010
Auxillary -> Auxiliary
5 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
1. Bluefin AUV Communication Extensions
Auxillary -> Auxiliary
5 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
* Website: http://www.bluefinrobotics.com
* Extensions: 1011
Auxillary -> Auxiliary
5 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
1. Dynamic Compact Control Language
Auxillary -> Auxiliary
5 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
* Website: http://github.com/GobySoft/dccl
* Extensions: 1012
Auxillary -> Auxiliary
5 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
1. ScaleOut StateServer® Native C++ API
Auxillary -> Auxiliary
5 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
* Website: http://www.scaleoutsoftware.com
* Extensions: 1013
Auxillary -> Auxiliary
5 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
1. FoundationDB SQL Layer
Auxillary -> Auxiliary
5 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
* Website: https://github.com/FoundationDB/sql-layer
* Extensions: 1014
Auxillary -> Auxiliary
5 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
1. Fender
Auxillary -> Auxiliary
5 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
* Website: https://github.com/hassox/fender
* Extensions: 1015
Auxillary -> Auxiliary
5 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
1. Vortex
Auxillary -> Auxiliary
5 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
* Website: http://www.prismtech.com/vortex
* Extensions: 1016
Auxillary -> Auxiliary
5 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
1. tresorit
Auxillary -> Auxiliary
5 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
* Website: https://tresorit.com/
* Extensions: 1017
Auxillary -> Auxiliary
5 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
1. CRIU (Checkpoint Restore In Userspace)
Auxillary -> Auxiliary
5 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
* Website: http://criu.org/Main_Page
* Extensions: 1018
Auxillary -> Auxiliary
5 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
1. protobuf-c
Auxillary -> Auxiliary
5 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
* Website: https://github.com/protobuf-c/protobuf-c
* Extensions: 1019
Auxillary -> Auxiliary
5 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
1. ScalaPB
Auxillary -> Auxiliary
5 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
* Website: https://scalapb.github.io/
* Extensions: 1020
Auxillary -> Auxiliary
5 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
1. protoc-gen-bq-schema
Auxillary -> Auxiliary
5 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
* Website: https://github.com/GoogleCloudPlatform/protoc-gen-bq-schema
* Extensions: 1021
Auxillary -> Auxiliary
5 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
1. grpc-gateway
Auxillary -> Auxiliary
5 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
* Website: https://github.com/gengo/grpc-gateway
* Extensions: 1022
Auxillary -> Auxiliary
5 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
1. Certificate Transparency
Auxillary -> Auxiliary
5 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
* Website: https://github.com/google/certificate-transparency
* Extensions: 1023
Auxillary -> Auxiliary
5 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
1. JUNOS Router Telemetry
Auxillary -> Auxiliary
5 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
* Website: http://www.juniper.net
* Extensions: 1024
Auxillary -> Auxiliary
5 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
1. Spine Event Engine
Auxillary -> Auxiliary
5 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
* Website: https://github.com/SpineEventEngine/core-java
* Extensions: 1025
Auxillary -> Auxiliary
5 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
1. Aruba cloud platform
Auxillary -> Auxiliary
5 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
* Website: ???
* Extensions: 1026 -> 1030
Auxillary -> Auxiliary
5 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
1. Voltha
Auxillary -> Auxiliary
5 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
* Website: ???
* Extensions: 1031 -> 1033
Auxillary -> Auxiliary
5 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
1. gator
Auxillary -> Auxiliary
5 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
* Website: ???
* Extensions: 1034
Reserve 1087 for Wire wire_package release notes: no
4 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
1. protoc-gen-flowtypes
Reserve 1088 for Confluent Schema Registry
4 years ago
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
* Website:
https://github.com/tmc/grpcutil/tree/master/protoc-gen-flowtypes
* Extensions: 1035
1. ProfaneDB
* Website: https://gitlab.com/ProfaneDB/ProfaneDB
* Extensions: 1036
1. protobuf-net
* Website: https://github.com/mgravell/protobuf-net
* Extensions: 1037
1. FICO / StreamEngine
* Website: http://www.fico.com/
* Extensions: 1038
1. GopherJS
* Website: https://github.com/johanbrandhorst/protobuf
* Extensions: 1039
1. ygot
* Website: https://github.com/openconfig/ygot
Add additional field number allocations for ygot. (#11518) ``` * (M) docs/options.md - Add two addition field options that are used as markers for specific YANG types in generated protobufs. ``` This adds two additional unique `FieldOptions` field numbers for annotat YANG leaf-lists, and leaf-lists of unions that need specific handling in field option code. Definitions for these fields are in github.com/openconfig/ygygot, particularly https://github.com/openconfig/ygot/blob/master/proto/yext/yext.proto. Closes #11518 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11518 from robshakir:main ea73e697e7fe4ba3bcb864d5c09d8ae1f25976f6 PiperOrigin-RevId: 502245756
2 years ago
* Extensions: 1040, 1179, 1180
Add custom option numbers for use by Buf (#11110) We are requesting a range of numbers instead of just one since we have some plans for a variety of orthogonal kinds of custom options. For example: 1. Injecting extra metadata into FileDescriptorProtos via custom options. (These options are inserted by the Buf tool when building proto sources, to encode additional metadata about the unit of files compiled.) 2. Configuration options for protoc plugins, that generate extra metadata into sources. (These options may be used by users when writing proto sources.) The suggested approach of reserving just one number and making it a message that contains *all* options is unattractive since users of one category of options is unlikely to want to import types related to another category. FWIW, there are several other rows above that have also chosen to reserve ranges of 5 or 10 numbers. Closes #11110 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11110 from jhump:jh/custom-options-for-buf-and-connect 68ef5ff1daa66fb471cdbfdacb936267751cf219 PiperOrigin-RevId: 492211135
2 years ago
1. go-grpcmw
* Website: https://github.com/MarquisIO/go-grpcmw
* Extensions: 1041
1. grpc-gateway protoc-gen-swagger
* Website: https://github.com/grpc-ecosystem/grpc-gateway
* Extensions: 1042
1. AN Message
* Website: TBD
* Extensions: 1043
1. protofire
* Website: https://github.com/ribrdb/protofire
* Extensions: 1044
1. Gravity
* Website: https://github.com/aphysci/gravity
* Extensions: 1045
1. SEMI Standards – I&C Technical Committee
* Website:
http://downloads.semi.org/web/wstdsbal.nsf/9c2b317e76523cca88257641005a47f5/88a5863a580e323088256e7b00707489!OpenDocument
* Extensions: 1046
1. Elixir plugin
* Website: https://github.com/tony612/grpc-elixir
* Extensions: 1047
1. API client generators
* Website: ???
* Extensions: 1048-1056
1. Netifi Proteus
* Website: https://github.com/netifi-proteus
* Extensions: 1057
1. CGSN Mooring Project
* Website: https://bitbucket.org/ooicgsn/cgsn-mooring
* Extensions: 1058
1. Container Storage Interface
* Website: https://github.com/container-storage-interface/spec
* Extensions: 1059-1069
1. TwirpQL Plugin
* Website: https://twirpql.dev
* Extensions: 1070
1. Protoc-gen-validate
* Website: https://github.com/bufbuild/protoc-gen-validate
* Extensions: 1071
1. Protokt
* Website: https://github.com/open-toast/protokt
* Extensions: 1072
1. Dart port of protocol buffers
* Website https://github.com/dart-lang/protobuf
* Extensions: 1073
1. Ocaml-protoc-plugin
* Website: https://github.com/issuu/ocaml-protoc-plugin
* Extensions: 1074
1. Analyze Re Graphene
* Website: https://analyzere.com
* Extensions: 1075
1. Wire since and until
* Website: https://square.github.io/wire/
* Extensions: 1076, 1077
1. Bazel, Failure Details
* Website: https://github.com/bazelbuild/bazel
* Extensions: 1078
1. grpc-graphql-gateway
* Website: https://github.com/ysugimoto/grpc-graphql-gateway
* Extensions: 1079
1. Cloudstate
* Website: https://cloudstate.io
* Extensions: 1080-1084
1. SummaFT protoc-plugins
* Website: https://summaft.com/
* Extensions: 1085
1. ADLINK EdgeSDK
* Website: https://www.adlinktech.com/en/Edge-SDK-IoT
* Extensions: 1086
1. Wire wire_package
* Website: https://square.github.io/wire/
* Extensions: 1087
1. Confluent Schema Registry
* Website: https://github.com/confluentinc/schema-registry
* Extensions: 1088
1. ScalaPB Validate
* Website: https://scalapb.github.io/docs/validation
* Extension: 1089
1. Astounding (Currently Private)
* Website: https://github.com/PbPipes/Astounding
* Extension: 1090
1. Protoc-gen-psql
* Website: https://github.com/Intrinsec/protoc-gen-psql
* Extension: 1091-1101
1. Protoc-gen-sanitize
* Website: https://github.com/Intrinsec/protoc-gen-sanitize
* Extension: 1102-1106
1. Coach Client Connect (planned release in March 2021)
* Website: https://www.coachclientconnect.com
* Extension: 1107
1. Kratos API Errors
* Website: https://go-kratos.dev
* Extension: 1108
1. Glitchdot (Currently Private)
* Website: https://go.glitchdot.com
* Extension: 1109
1. eigr/protocol
* Website: https://eigr.io
* Extension: 1110-1114
1. Container Object Storage Interface (COSI)
* Website:
https://github.com/kubernetes-sigs/container-object-storage-interface-spec
* Extension: 1115-1124
1. Protoc-gen-jsonschema
* Website: https://github.com/chrusty/protoc-gen-jsonschema
* Extension: 1125-1129
1. Protoc-gen-checker
* Website: https://github.com/Intrinsec/protoc-gen-checker
* Extension: 1130-1139
1. Protoc-gen-go-svc
* Website: https://github.com/dane/protoc-gen-go-svc
* Extension: 1140
1. Embedded Proto
* Website: https://EmbeddedProto.com
* Extension: 1141
1. Protoc-gen-fieldmask
* Website: https://github.com/yeqown/protoc-gen-fieldmask
* Extension: 1142
1. Google Gnostic
* Website: https://github.com/google/gnostic
* Extension: 1143
1. Protoc-gen-go-micro
* Website: https://github.com/unistack-org/protoc-gen-go-micro
* Extension: 1144
1. Protoc-gen-authz
* Website: https://github.com/Neakxs/protoc-gen-authz
* Extension: 1145
1. Protonium
* Website: https://github.com/zyp/protonium
* Extension: 1146
1. Protoc-gen-xo
* Website: https://github.com/xo/ecosystem
* Extension: 1147
1. Ballerina gRPC
* Website: https://github.com/ballerina-platform/module-ballerina-grpc
* Extension: 1148
1. Protoc-gen-referential-integrity
* Website:
https://github.com/ComponentCorp/protoc-gen-referential-integrity
* Extension: 1149
1. Oclea Service Layer RPC
* Website: https://oclea.com/
* Extension: 1150
1. mypy-protobuf
* Website: https://github.com/nipunn1313/mypy-protobuf
* Extension: 1151-1154
1. Pigweed protobuf compiler
* Website: https://pigweed.dev/pw_protobuf
* Extension: 1155
1. Perfetto
* Website: https://perfetto.dev
* Extension: 1156
1. Buf
* Website: http://buf.build/
* Extension: 1157-1166
1. Connect
* Website: http://connect.build/
* Extension: 1167-1176
Internal change COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11257 from Neakxs:apply-registration-for-protocel-extensions 8d04626e85c44ca8ba812c8ccb12585b92cb6d6d PiperOrigin-RevId: 494841129
2 years ago
1. protocel
* Website: https://github.com/Neakxs/protocel
* Extension: 1177-1178
Add Cybozu to options.md (#12324) Hello. We want to make our protobuf repository public which contains a custom extension. Our code is already available at https://github.com/cybozu/protobuf. Please let us use extension number 1179. Regards, Closes #12324 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/12324 from ymmt2005:patch-1 b0a5171211d1785b7df1d0ccdc725b2a9db9eecd PiperOrigin-RevId: 519022489
2 years ago
1. Cybozu
* Website: https://github.com/cybozu/protobuf
* Extension: 1179
Reserve 1180 for Wire use_array (#12491) release notes: no Supports https://github.com/square/wire/pull/2433 Closes #12491 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/12491 from JGulbronson:jgulbronson.claim-1180-for-wire f577336c0b7455930de8b7fbb727ac2003f8c359 PiperOrigin-RevId: 525793344
2 years ago
1. Wire use_array
* Website: https://square.github.io/wire/
* Extensions: 1180
Reserve option for EngFlow (#12599) Closes #12599 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/12599 from Yannic:patch-4 80578955ca3c565ba7a424cdbede9132e63fd14d PiperOrigin-RevId: 528576745
2 years ago
1. EngFlow
* Website: https://github.com/EngFlow/engflowapis
* Extensions: 1181
Reserve option for proto-telemetry (#12758) Hello! I'm looking to reserve an option for a project I'm calling proto-telemetry. It will create open-telemetry compatible functions that add attributes to a span. Once this is accepted I'll update the project to use the reserved option number. Thanks so much! Closes #12758 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/12758 from clly:proto-telemetry a8b38762d7e26b1870698517e2e02a0ac98bfc60 PiperOrigin-RevId: 532305028
2 years ago
1. Proto-telemetry
* Website: https://github.com/clly/proto-telemetry
* Extensions: 1182
Add Protobuf extension number for DTDL option (#13247) This option will be used by extensions to the [Digital Twins Definition Language](https://github.com/Azure/opendigitaltwins-dtdl) to support Protobuf serialization. Closes #13247 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/13247 from jrdouceur:jrdouceur/dtdl-option 84192710c743d8435639fa8508174cec87a7dc8a PiperOrigin-RevId: 547186193
1 year ago
1. Digital Twins Definition Language (DTDL)
* Website: https://github.com/Azure/opendigitaltwins-dtdl
* Extensions: 1183