roto/codegen/data/request.bin

&proto/google/protobuf/descriptor.proto"
"zȇ
&proto/google/protobuf/descriptor.protogoogle.protobuf"]
FileDescriptorSet8
file
 (2$.google.protobuf.FileDescriptorProtoRfile*€ìÊÿ
�ìÊÿ
"Å
FileDescriptorProto
name
 
(	Rname
package 
(	Rpackage

dependency (	R
dependency+
public_dependency
 (RpublicDependency'
weak_dependency (RweakDependency+
option_dependency (	RoptionDependencyC
message_type (2 .google.protobuf.DescriptorProtoRmessageTypeA
	enum_type (2$.google.protobuf.EnumDescriptorProtoRenumTypeA
service (2'.google.protobuf.ServiceDescriptorProtoRserviceC
	extension (2%.google.protobuf.FieldDescriptorProtoR	extension6
options 
(2.google.protobuf.FileOptionsRoptionsI
source_code_info	 
(2.google.protobuf.SourceCodeInfoRsourceCodeInfo
syntax 
(	Rsyntax2
edition 
(2.google.protobuf.EditionRedition"ü
DescriptorProto
name
 
(	Rname;
field (2%.google.protobuf.FieldDescriptorProtoRfieldC
	extension (2%.google.protobuf.FieldDescriptorProtoR	extensionA
nested_type (2 .google.protobuf.DescriptorProtoR
nestedTypeA
	enum_type (2$.google.protobuf.EnumDescriptorProtoRenumTypeX
extension_range (2/.google.protobuf.DescriptorProto.ExtensionRangeRextensionRangeD

oneof_decl (2%.google.protobuf.OneofDescriptorProtoR	oneofDecl9
options 
(2.google.protobuf.MessageOptionsRoptionsU
reserved_range	 (2..google.protobuf.DescriptorProto.ReservedRangeR
reservedRange#

reserved_name
 (	RreservedNameA

visibility 
(2!.google.protobuf.SymbolVisibilityR
visibilityz
ExtensionRange
start
 
(Rstart
end 
(Rend@
options 
(2&.google.protobuf.ExtensionRangeOptionsRoptions7

ReservedRange
start
 
(Rstart
end 
(Rend"Ô
ExtensionRangeOptionsX
uninterpreted_optionç (2$.google.protobuf.UninterpretedOptionRuninterpretedOptionY
declaration (22.google.protobuf.ExtensionRangeOptions.DeclarationBˆ
Rdeclaration7
features2 
(2.google.protobuf.FeatureSetRfeaturesm
verification 
(28.google.protobuf.ExtensionRangeOptions.VerificationState:
UNVERIFIEDBˆ
Rverification”

Declaration
number
 
(Rnumber
	full_name 
(	RfullName
type 
(	Rtype
reserved 
(Rreserved
repeated 
(RrepeatedJ"4
VerificationState
DECLARATION

UNVERIFIED
*Þç*	耀€€"Á
FieldDescriptorProto
name
 
(	Rname
number 
(RnumberA
label 
(2+.google.protobuf.FieldDescriptorProto.LabelRlabel>
type 
(2*.google.protobuf.FieldDescriptorProto.TypeRtype
	type_name 
(	RtypeName
extendee 
(	Rextendee#

default_value 
(	RdefaultValue
oneof_index	 
(R
oneofIndex
	json_name
 
(	RjsonName7
options 
(2.google.protobuf.FieldOptionsRoptions'
proto3_optional 
(Rproto3Optional"¶
Type
TYPE_DOUBLE


TYPE_FLOAT

TYPE_INT64
TYPE_UINT64

TYPE_INT32
TYPE_FIXED64
TYPE_FIXED32
	TYPE_BOOL
TYPE_STRING	

TYPE_GROUP

TYPE_MESSAGE

TYPE_BYTES
TYPE_UINT32

	TYPE_ENUM

TYPE_SFIXED32

TYPE_SFIXED64
TYPE_SINT32
TYPE_SINT64"C
Label
LABEL_OPTIONAL

LABEL_REPEATED
LABEL_REQUIRED"c
OneofDescriptorProto
name
 
(	Rname7
options 
(2.google.protobuf.OneofOptionsRoptions"¦
EnumDescriptorProto
name
 
(	Rname?
value (2).google.protobuf.EnumValueDescriptorProtoRvalue6
options 
(2.google.protobuf.EnumOptionsRoptions]
reserved_range (26.google.protobuf.EnumDescriptorProto.EnumReservedRangeR
reservedRange#

reserved_name (	RreservedNameA

visibility 
(2!.google.protobuf.SymbolVisibilityR
visibility;
EnumReservedRange
start
 
(Rstart
end 
(Rend"ƒ

EnumValueDescriptorProto
name
 
(	Rname
number 
(Rnumber;
options 
(2!.google.protobuf.EnumValueOptionsRoptions"µ

ServiceDescriptorProto
name
 
(	Rname>
method (2&.google.protobuf.MethodDescriptorProtoRmethod9
options 
(2.google.protobuf.ServiceOptionsRoptionsJRstream"‰
MethodDescriptorProto
name
 
(	Rname

input_type 
(	R	inputType
output_type 
(	R
outputType8
options 
(2.google.protobuf.MethodOptionsRoptions0
client_streaming 
(:falseRclientStreaming0
server_streaming 
(:falseRserverStreaming"ü

FileOptions!
java_package
 
(	RjavaPackage0
java_outer_classname 
(	RjavaOuterClassnameù

java_multiple_files
 
(:falseBÁ
²
½
æ é*´
This behavior is enabled by default in editions 2024 and above. To disable it, you can set `features.(pb.java).nest_in_file_class = YES` on individual messages, enums, or services.RjavaMultipleFilesD
java_generate_equals_and_hash 
(B
RjavaGenerateEqualsAndHash:
java_string_check_utf8 
(:falseRjavaStringCheckUtf8S
optimize_for	 
(2).google.protobuf.FileOptions.OptimizeMode:SPEEDRoptimizeFor

go_package 
(	R	goPackage5
cc_generic_services 
(:falseRccGenericServices9
java_generic_services 
(:falseRjavaGenericServices5
py_generic_services 
(:falseRpyGenericServices%

deprecated 
(:falseR
deprecated.
cc_enable_arenas 
(:trueRccEnableArenas*
objc_class_prefix$ 
(	RobjcClassPrefix)
csharp_namespace% 
(	RcsharpNamespace!
swift_prefix' 
(	RswiftPrefix(
php_class_prefix( 
(	RphpClassPrefix#

php_namespace) 
(	RphpNamespace4
php_metadata_namespace, 
(	RphpMetadataNamespace!
ruby_package- 
(	RrubyPackage7
features2 
(2.google.protobuf.FeatureSetRfeaturesX
uninterpreted_optionç (2$.google.protobuf.UninterpretedOptionRuninterpretedOption":
OptimizeMode	
SPEED

	CODE_SIZE
LITE_RUNTIME*Þç*	耀€€J*+J&'Rphp_generic_services"ü
MessageOptions<
message_set_wire_format
 
(:falseRmessageSetWireFormatL
no_standard_descriptor_accessor 
(:falseRnoStandardDescriptorAccessor%

deprecated 
(:falseR
deprecated
	map_entry 
(RmapEntryV
&deprecated_legacy_json_field_conflicts 
(B
R"deprecatedLegacyJsonFieldConflicts7
features 
(2.google.protobuf.FeatureSetRfeaturesX
uninterpreted_optionç (2$.google.protobuf.UninterpretedOptionRuninterpretedOption*Þç*	耀€€JJJJ	J	
"Î
FieldOptionsA
ctype
 
(2#.google.protobuf.FieldOptions.CType:STRINGRctype
packed 
(RpackedG
jstype 
(2$.google.protobuf.FieldOptions.JSType:	JS_NORMALRjstype
lazy 
(:falseRlazy.
unverified_lazy 
(:falseRunverifiedLazy%

deprecated 
(:falseR
deprecated
weak
 
(:falseB
Rweak(
debug_redact 
(:falseRdebugRedactK
	retention 
(2-.google.protobuf.FieldOptions.OptionRetentionR	retentionH
targets (2..google.protobuf.FieldOptions.OptionTargetTypeRtargetsW
edition_defaults (2,.google.protobuf.FieldOptions.EditionDefaultReditionDefaults7
features 
(2.google.protobuf.FeatureSetRfeaturesU
feature_support 
(2,.google.protobuf.FieldOptions.FeatureSupportRfeatureSupportX
uninterpreted_optionç (2$.google.protobuf.UninterpretedOptionRuninterpretedOptionZ
EditionDefault2
edition 
(2.google.protobuf.EditionRedition
value 
(	Rvalue»
FeatureSupportG
edition_introduced
 
(2.google.protobuf.EditionReditionIntroducedG
edition_deprecated 
(2.google.protobuf.EditionReditionDeprecated/
deprecation_warning 
(	RdeprecationWarningA
edition_removed 
(2.google.protobuf.EditionReditionRemoved#

removal_error 
(	RremovalError"/
CType

STRING
CORD

STRING_PIECE"5
JSType
	JS_NORMAL
	JS_STRING

	JS_NUMBER"U
OptionRetention
RETENTION_UNKNOWN
RETENTION_RUNTIME

RETENTION_SOURCE"Œ
OptionTargetType
TARGET_TYPE_UNKNOWN
TARGET_TYPE_FILE

TARGET_TYPE_EXTENSION_RANGE
TARGET_TYPE_MESSAGE
TARGET_TYPE_FIELD
TARGET_TYPE_ONEOF
TARGET_TYPE_ENUM
TARGET_TYPE_ENUM_ENTRY
TARGET_TYPE_SERVICE
TARGET_TYPE_METHOD	*Þç*	耀€€JJ"´

OneofOptions7
features
 
(2.google.protobuf.FeatureSetRfeaturesX
uninterpreted_optionç (2$.google.protobuf.UninterpretedOptionRuninterpretedOption*Þç*	耀€€"Ù
EnumOptions
allow_alias 
(R
allowAlias%

deprecated 
(:falseR
deprecatedV
&deprecated_legacy_json_field_conflicts 
(B
R"deprecatedLegacyJsonFieldConflicts7
features 
(2.google.protobuf.FeatureSetRfeaturesX
uninterpreted_optionç (2$.google.protobuf.UninterpretedOptionRuninterpretedOption*Þç*	耀€€J"â
EnumValueOptions%

deprecated
 
(:falseR
deprecated7
features 
(2.google.protobuf.FeatureSetRfeatures(
debug_redact 
(:falseRdebugRedactU
feature_support 
(2,.google.protobuf.FieldOptions.FeatureSupportRfeatureSupportX
uninterpreted_optionç (2$.google.protobuf.UninterpretedOptionRuninterpretedOption*Þç*	耀€€"Ý

ServiceOptions7
features" 
(2.google.protobuf.FeatureSetRfeatures%

deprecated! 
(:falseR
deprecatedX
uninterpreted_optionç (2$.google.protobuf.UninterpretedOptionRuninterpretedOption*Þç*	耀€€"¡

MethodOptions%

deprecated! 
(:falseR
deprecatedq
idempotency_level" 
(2/.google.protobuf.MethodOptions.IdempotencyLevel:IDEMPOTENCY_UNKNOWNRidempotencyLevel7
features# 
(2.google.protobuf.FeatureSetRfeaturesX
uninterpreted_optionç (2$.google.protobuf.UninterpretedOptionRuninterpretedOption"P
IdempotencyLevel
IDEMPOTENCY_UNKNOWN
NO_SIDE_EFFECTS


IDEMPOTENT*Þç*	耀€€"š
UninterpretedOptionA
name (2-.google.protobuf.UninterpretedOption.NamePartRname)
identifier_value 
(	RidentifierValue,
positive_int_value 
(RpositiveIntValue,
negative_int_value 
(RnegativeIntValue!
double_value 
(
RdoubleValue!
string_value 
(RstringValue'
aggregate_value 
(	RaggregateValueJ
NamePart
	name_part
 (	RnamePart!
is_extension (RisExtension"ñ

FeatureSet‘

field_presence
 
(2).google.protobuf.FeatureSet.FieldPresenceB?ˆ

˜
˜

¢

EXPLICIT„¢

IMPLICITç¢

EXPLICITè²
èR
fieldPresencel
	enum_type 
(2$.google.protobuf.FeatureSet.EnumTypeB)ˆ

˜
˜

¢
CLOSED„¢
	OPENç²
èRenumType˜

repeated_field_encoding 
(21.google.protobuf.FeatureSet.RepeatedFieldEncodingB-ˆ

˜
˜

¢

EXPANDED„¢
PACKEDç²
èRrepeatedFieldEncoding~
utf8_validation 
(2*.google.protobuf.FeatureSet.Utf8ValidationB)ˆ

˜
˜

¢
	NONE„¢
VERIFYç²
èRutf8Validation~
message_encoding 
(2+.google.protobuf.FeatureSet.MessageEncodingB&ˆ

˜
˜

¢
LENGTH_PREFIXED„²
èRmessageEncoding‚

json_format 
(2&.google.protobuf.FeatureSet.JsonFormatB9ˆ

˜
˜
˜

¢
LEGACY_BEST_EFFORT„¢

ALLOWç²
èR
jsonFormat¼

enforce_naming_style 
(2..google.protobuf.FeatureSet.EnforceNamingStyleBZˆ
˜

˜
˜
˜
˜
˜
˜
˜
˜
	¢
STYLE_LEGACY„¢
	STYLE2024é¢
	STYLE2026ê²
éRenforceNamingStyle¹

default_symbol_visibility 
(2E.google.protobuf.FeatureSet.VisibilityFeature.DefaultSymbolVisibilityB6ˆ
˜

¢

EXPORT_ALL„¢
EXPORT_TOP_LEVELé²
éRdefaultSymbolVisibilityÃ

enforce_proto_limits	 
(2A.google.protobuf.FeatureSet.ProtoLimitsFeature.EnforceProtoLimitsBNˆ
˜
˜
˜
˜
¢
LEGACY_NO_EXPLICIT_LIMITS„¢
PROTO_LIMITS2026ê²
êRenforceProtoLimits¡

VisibilityFeature"�

DefaultSymbolVisibility%
!DEFAULT_SYMBOL_VISIBILITY_UNKNOWN

EXPORT_ALL

EXPORT_TOP_LEVEL
	LOCAL_ALL

STRICTJ
€€€€y
ProtoLimitsFeature"c
EnforceProtoLimits
PROTO_LIMITS_UNKNOWN
LEGACY_NO_EXPLICIT_LIMITS

PROTO_LIMITS2026"\

FieldPresence
FIELD_PRESENCE_UNKNOWN
EXPLICIT

IMPLICIT
LEGACY_REQUIRED"7
EnumType
ENUM_TYPE_UNKNOWN
OPEN


CLOSED"V
RepeatedFieldEncoding#
REPEATED_FIELD_ENCODING_UNKNOWN

PACKED

EXPANDED"I
Utf8Validation
UTF8_VALIDATION_UNKNOWN

VERIFY
NONE"

"S
MessageEncoding
MESSAGE_ENCODING_UNKNOWN
LENGTH_PREFIXED

	DELIMITED"H

JsonFormat
JSON_FORMAT_UNKNOWN	
ALLOW

LEGACY_BEST_EFFORT"f
EnforceNamingStyle 
ENFORCE_NAMING_STYLE_UNKNOWN
	STYLE2024

STYLE_LEGACY
	STYLE2026*è‹N*‹N�N*�N‘NJçè"ï
FeatureSetDefaultsX
defaults
 (2<.google.protobuf.FeatureSetDefaults.FeatureSetEditionDefaultRdefaultsA
minimum_edition 
(2.google.protobuf.EditionRminimumEditionA
maximum_edition 
(2.google.protobuf.EditionRmaximumEditionø

FeatureSetEditionDefault2
edition 
(2.google.protobuf.EditionReditionN
overridable_features 
(2.google.protobuf.FeatureSetRoverridableFeaturesB
fixed_features 
(2.google.protobuf.FeatureSetR
fixedFeaturesJ
JRfeatures"·
SourceCodeInfoD
location
 (2(.google.protobuf.SourceCodeInfo.LocationRlocationÎ

Location
path
 (B
Rpath
span (B
Rspan)
leading_comments 
(	RleadingComments+
trailing_comments 
(	RtrailingComments:
leading_detached_comments (	RleadingDetachedComments*€ìÊÿ
�ìÊÿ
"Ð
GeneratedCodeInfoM

annotation
 (2-.google.protobuf.GeneratedCodeInfo.AnnotationR
annotationë


Annotation
path
 (B
Rpath
source_file 
(	R
sourceFile
begin 
(Rbegin
end 
(RendR
semantic 
(26.google.protobuf.GeneratedCodeInfo.Annotation.SemanticRsemantic"(
Semantic
NONE
SET
	
ALIAS*Ñ
Edition
EDITION_UNKNOWN
EDITION_LEGACY„
EDITION_PROTO2æ
EDITION_PROTO3ç
EDITION_2023è
EDITION_2024é
EDITION_2026ê
EDITION_UNSTABLE�N
EDITION_1_TEST_ONLY

EDITION_2_TEST_ONLY
EDITION_99997_TEST_ONLY��
EDITION_99998_TEST_ONLYž�
EDITION_99999_TEST_ONLYŸ�
EDITION_MAXÿÿÿÿ*U
SymbolVisibility
VISIBILITY_UNSET
VISIBILITY_LOCAL

VISIBILITY_EXPORTB~
com.google.protobufBDescriptorProtosH
Z-google.golang.org/protobuf/types/descriptorpbø

¢GPBªGoogle.Protobuf.ReflectionJßô
â

ò

2‰ Protocol Buffers - Google's data interchange format
 Copyright 2008 Google LLC.  All rights reserved.

 Use of this source code is governed by a BSD-style
 license that can be found in the LICENSE file or at
 https://developers.google.com/open-source/licenses/bsd
2Û Author: kenton@google.com (Kenton Varda)
  Based on original Protocol Buffers design by
  Sanjay Ghemawat, Jeff Dean, and others.

 The messages in this file describe the definitions found in .proto files.
 A valid .proto file can be translated directly to a FileDescriptorProto
 without any other information (e.g. without reading its imports).






D
	
D


,
	

,


1
	
1


7
	
%7


!
	
$!



	





	t descriptor.proto must be optimized for speed because reflection-based
 algorithms don't work during bootstrapping.

j
 )
^ The protocol compiler can output a FileDescriptorSet containing the .proto
 files it parses.




 

!(

!


!


!#

!&'
&
$( Extensions for tooling.


$



$


$


$(
-
,Q
! The full set of known editions.




,
:
.- A placeholder for an unknown edition value.



.

.
™


2‹
 A placeholder edition for specifying default behaviors *before* a feature
 was first introduced.  This is effectively an "infinite past".




2


2
‚
8ô
 Legacy syntax "editions".  These pre-date editions, but behave much like
 distinct editions.  These can't be used to specify the edition of proto
 files, but feature definitions must supply proto2/proto3 defaults for
 backwards compatibility.



8

8

9


9

9
¯

>¡
 Editions that have been released.  The specific values are arbitrary and
 should not be depended on, but they will always be time-ordered for easy
 comparison.



>

>

?


?

?

@


@

@
U
CH A placeholder edition for developing and testing unscheduled features.



C

C
}
Gp Placeholder editions for testing feature resolution.  These should not be
 used or relied on outside of tests.



G

G

	H

	
H

	H


I"



I


I!

J"


J

J!

K"


K

K!
¸


Pª
 Placeholder for specifying unbounded edition support.  This should only
 ever be used by plugins that can expect to never require any changes to
 support a new edition.




P


P
0

T€

# Describes a complete .proto file.





T
9

U", file name, relative to root of source tree



U



U



U


U
*


V" e.g. "foo", "foo.bar", etc.




V




V




V



V
4

Y!' Names of files imported by this file.



Y



Y



Y


Y 
Q

[(D Indexes of the public imported files in the dependency list above.



[



[



["


[%'
z

^&m Indexes of the weak imported files in the dependency list.
 For Google-internal migration only. Do not use.



^



^



^ 


^#%
Ÿ


b)‘
 Names of files imported by this file purely for the purpose of providing
 option extensions. These are excluded from the dependency list above.



b



b



b#


b&(
6

e,) All top-level definitions in this file.



e



e



e'


e*+


f-


f



f



f(


f+,


g.


g



g!



g")


g,-


	h.


	h



	h


	
h )


	h,-



j#



j




j




j



j!"
ô


p/æ
 This field contains optional information about the original source code.
 You may safely remove this entire field without harming runtime
 functionality of the descriptors -- the information is needed only by
 development tools.



p



p



p*


p-.
ø

yê The syntax of the proto file.
 The supported values are "proto2", "proto3", and "editions".

 If `edition` is present, this value must be "editions".
 WARNING: This field should only be used by protobuf plugins or special
 cases like the proto compiler. Other uses are discouraged and
 developers should rely on the protoreflect APIs for their client language.



y



y



y


y
�


 ó
 The edition of the proto file.
 WARNING: This field should only be used by protobuf plugins or special
 cases like the proto compiler. Other uses are discouraged and
 developers should rely on the protoreflect APIs for their client language.



















)
ƒ
¦

 Describes a message type.



ƒ


„


„



„



„


„



†
*


†




†




†
 %


†
()

‡
.

‡



‡



‡
 )

‡
,-

‰
+

‰



‰



‰
&

‰
)*

Š
-

Š



Š



Š
(

Š
+,

Œ
‘



Œ



�
" Inclusive.


�


�




�


�



Ž
" Exclusive.



Ž



Ž





Ž



Ž


�
/

�


�

"


�
#*

�
-.

’
.

’



’



’
)

’
,-

”
/

”



”



”
 *

”
-.

–
&

–



–



–
!

–
$%
¬


›
ž
›
 Range of reserved tag numbers. Reserved tag numbers may not be used by
 fields or extension ranges in the same message. Reserved ranges may
 not overlap.




›




œ
" Inclusive.



œ



œ





œ



œ




�
" Exclusive.




�




�






�




�


Ÿ
,

Ÿ



Ÿ



Ÿ
'

Ÿ
*+
ƒ

	¢
%u Reserved field names, which may not be used by fields in the same message.
 A given name may only be reserved once.


	¢



	¢


	
¢


	¢
"$
C

¥
,5 Support for `export` and `local` keywords on enums.



¥




¥




¥
&


¥
)+

¨
ß




¨

’

«
„
 Range reserved for first-class custom options defined by the Protobuf
 team. User custom options must use the 1000+ range instead.


«




«



«

O
­
:A The parser stores options it doesn't recognize here. See above.


­



­



­
3

­
69

¯
Æ



¯


K
±
; The extension number declared within the extension range.


±


±




±


±

z

µ
"j The fully-qualified name of the extension field. There must be a leading
 dot in front of the full name.



µ



µ





µ



µ
 !
¡

º
�
 The fully-qualified type name of the extension field. Unlike
 Metadata.type, Declaration.type must have a leading dot for messages
 and enums.


º


º




º


º

Î

¿
½
 If true, indicates that the number is reserved in the extension range,
 and any extension field with the number will fail to compile. Set this
 when a declared extension field is deleted.


¿


¿




¿


¿

Š

Ã
z If true, indicates that the extension must be defined as repeated.
 Otherwise the extension must be defined as optional.


Ã


Ã




Ã


Ã

$
	Å
" removed is_repeated


	Å



	
Å



	Å


±


Ë
F¢
 For external users: DO NOT USE. We are in the process of open sourcing
 extension declaration and executing internal cleanups before it can be
 used externally.



Ë




Ë




Ë
"


Ë
%&


Ë
'E


Ë
(D
=
Î
$/ Any features defined in the specific edition.


Î



Î



Î


Î
!#
@
Ñ
Õ
0 The verification state of the extension range.



Ñ

C
Ó
3 All the extensions of the range must be declared.



Ó


Ó



Ô




Ô



Ô

Ž

Ú
Û
;~ The verification state of the range.
 TODO: flip the default to DECLARATION once all empty ranges
 are marked as UNVERIFIED.


Ú



Ú



Ú
)

Ú
,-

Û
:

Û


Û
9
Z
Þ
M Clients can define custom options in extensions of this message. See above.



Þ





Þ




Þ

3
â
Ê
% Describes a field within a message.



â


ã
ƒ


ã

S
æ
C 0 is reserved for errors.
 Order is weird for historical reasons.



æ


æ



ç




ç



ç

w
ê
g Not ZigZag encoded.  Negative numbers take 10 bytes.  Use TYPE_SINT64 if
 negative values are likely.



ê


ê


ë



ë


ë

w
î
g Not ZigZag encoded.  Negative numbers take 10 bytes.  Use TYPE_SINT32 if
 negative values are likely.



î


î


ï



ï


ï


ð



ð


ð


ñ



ñ


ñ


ò



ò


ò

Æ
	ø
µ Tag-delimited aggregate.
 Group type is deprecated and not supported after google.protobuf. However, Proto3
 implementations should still be able to parse the group wire format and
 treat group fields as unknown fields.  In Editions, the group wire format
 can be enabled via the `message_encoding` feature.


	
ø


	ø

-

ù
" Length-delimited aggregate.




ù



ù

#
ü
 New in version 2.



ü


ü


ý



ý


ý



þ




þ



þ


ÿ



ÿ


ÿ


€


€

€
'
�" Uses ZigZag encoding.



�

�
'
‚" Uses ZigZag encoding.



‚

‚


…�



…
*

‡ 0 is reserved for errors




‡


‡



ˆ




ˆ



ˆ
Ì


Œ»
 The required label is only allowed in google.protobuf.  In proto3 and Editions
 it's explicitly prohibited.  In Editions, the `field_presence` feature
 can be used to get this behavior.




Œ


Œ

�

�


�


�

�


�


�



�



�


�

‘

‘


‘


‘

‘
œ

•�
 If type_name is set, this need not be set.  If both this and type_name
 are set, this must be one of TYPE_ENUM, TYPE_MESSAGE or TYPE_GROUP.


•


•


•

•
·
œ ¨ For message and enum types, this is the name of the type.  If the name
 starts with a '.', it is fully-qualified.  Otherwise, C++-like scoping
 rules are used to find the type (i.e. first the nested types within this
 message are searched, then within the parent, on up to the root
 namespace).


œ


œ


œ

œ
~
 p For extensions, this is the name of the type being extended.  It is
 resolved in the same manner as type_name.


 


 


 

 
‘
¦$‚ For numeric types, contains the original text representation of the value.
 For booleans, "true" or "false".
 For strings, contains the default text contents (not escaped in any way).
 For bytes, contains the C escaped value.  All bytes >= 128 are escaped.


¦


¦


¦

¦"#
„

ª!v If set, gives the index of a oneof in the containing type's oneof_decl
 list.  This field is a member of that oneof.


ª


ª


ª

ª 
ú

°!ë
 JSON name of this field. The value is set by protocol compiler. If the
 user has set a "json_name" option on this field, that option's value
 will be used. Otherwise, it's deduced from the field's name by converting
 it to camelCase.


°


°


°

° 

	²$

	²


	²

	
²

	²"#
°	

É%¡	 If true, this is a proto3 "optional". When a proto3 field is optional, it
 tracks presence regardless of field type.

 When proto3_optional is true, this field must belong to a oneof to signal
 to old proto3 clients that presence is tracked for this field. This oneof
 is known as a "synthetic" oneof, and this field must be its sole member
 (each proto3 optional field gets its own synthetic oneof). Synthetic oneofs
 exist in the descriptor only, and do not generate any API. Synthetic oneofs
 must be ordered after all "real" oneofs.

 For message fields, proto3_optional doesn't create any semantic change,
 since non-repeated message fields always track presence. However it still
 indicates the semantic detail of whether the user wrote "optional" or not.
 This can be useful for round-tripping the .proto file. For consistency we
 give message fields a synthetic oneof also, even though it is not required
 to track presence. This is especially important because the parser can't
 tell if a field is a message or an enum, so it must always create a
 synthetic oneof.

 Proto2 optional fields do not set this flag, because they already indicate
 optional with `LABEL_OPTIONAL`.



É



É



É


É"$
"
ÍÐ
 Describes a oneof.



Í

Î

Î


Î


Î

Î


Ï$


Ï



Ï



Ï


Ï"#
'
Óð
 Describes an enum type.



Ó

Ô

Ô


Ô


Ô

Ô


Ö.


Ö



Ö#



Ö$)


Ö,-

Ø#

Ø


Ø


Ø

Ø!"
¯
àãž Range of reserved numeric values. Reserved values may not be used by
 entries in the same enum. Reserved ranges may not overlap.

 Note that this is distinct from DescriptorProto.ReservedRange in that it
 is inclusive such that it can appropriately represent the entire int32
 domain.



à


á" Inclusive.


á

á



á

á


â" Inclusive.



â


â




â


â
ª

è0›
 Range of reserved numeric values. Reserved numeric values may not be used
 by enum values in the same enum declaration. Reserved ranges may not
 overlap.


è


è


è+

è./
l
ì$^ Reserved enum value names, which may not be reused. A given name may only
 be reserved once.


ì


ì


ì

ì"#
C
ï+5 Support for `export` and `local` keywords on enums.


ï


ï


ï&

ï)*
1
óø
# Describes a value within an enum.



ó 

ô

ô


ô


ô

ô


õ


õ



õ



õ


õ

÷(

÷


÷


÷#

÷&'
$
ûƒ
 Describes a service.



û

ü

ü


ü


ü

ü


ý,


ý



ý 



ý!'


ý*+

ÿ&

ÿ


ÿ


ÿ!

ÿ$%

	�

	�

	
�

	�


‚


‚
0
	†”
" Describes a method of a service.


	
†

	‡

	‡


	‡

	
‡

	‡
—

	
‹!ˆ
 Input and output type names.  These are resolved in the same way as
 FieldDescriptorProto.type_name, but must refer to a message type.


	
‹


	
‹

	

‹

	
‹ 

	Œ"

	Œ


	Œ

	
Œ

	Π!

	Ž%

	Ž


	Ž

	
Ž 

	Ž#$
E
	‘77 Identifies if client streams multiple client messages


	‘


	‘

	
‘ 

	‘#$

	‘%6

	‘05
E
	“77 Identifies if server streams multiple server messages


	“


	“

	
“ 

	“#$

	“%6

	“05
¯

¶Ç
2N ===================================================================
 Options
2Ð
 Each of the definitions above may have "options" attached.  These are
 just annotations which may cause code to be generated slightly differently
 or may contain hints for code that manipulates protocol messages.

 Clients may define custom options as extensions of the *Options messages.
 These extensions may not yet be known at parsing time, so the parser cannot
 store the values in them.  Instead it stores them in a field in the *Options
 message called uninterpreted_option. This field must have the same name
 across all *Options messages. We then use this field to populate the
 extensions when we build a descriptor, at which point all protos have been
 parsed and so all extensions are known.

 Extension numbers for custom options may be chosen as follows:
 * For options which will only be used within a single application or
   organization, or for experimental options, use field numbers 50000
   through 99999.  It is up to you to ensure that you do not use the
   same number for multiple options.
 * For options which will be published and used publicly by multiple
   independent entities, e-mail protobuf-global-extension-registry@google.com
   to reserve extension numbers. Simply provide your project name (e.g.
   Objective-C plugin) and your project website (if available) -- there's no
   need to explain how you intend to use them. Usually you only need one
   extension number. You can declare multiple options with only one extension
   number by putting them in a sub-message. See the Custom Options section of
   the docs for examples:
   https://developers.google.com/protocol-buffers/docs/proto#options
   If this turns out to be popular, a web service will be set up
   to automatically assign option numbers.




¶
ô


¼#å
 Sets the Java package where classes generated from this .proto will be
 placed.  By default, the proto package is used, but this is often
 inappropriate because proto packages do not normally start with backwards
 domain names.



¼



¼



¼


¼!"
ñ


Ã+â Controls the name of the wrapper Java class generated for the .proto file.
 That class will always contain the .proto file's getDescriptor() method as
 well as any top-level extensions defined in the .proto file.
 If java_multiple_files is disabled, then all the other classes from the
 .proto file will be nested inside the single wrapper outer class.




Ã




Ã




Ã&



Ã)*
¨

ËÕ— If enabled, then the Java code generator will generate a separate .java
 file for each top-level message, enum, and service defined in the .proto
 file.  Thus, these types will *not* be nested inside the wrapper class
 named by java_outer_classname.  However, the wrapper class will still be
 generated to contain the file's getDescriptor() method as well as any
 top-level extensions defined in the file.



Ë



Ë



Ë#


Ë&(


Ë)Õ


Ì


ÍÔ
)

ØE This option does nothing.



Ø



Ø



Ø-


Ø02


Ø3D


Ø4C
Ï

ä>À A proto2 file can set this to true to opt in to UTF-8 checking for Java,
 which will throw an exception if invalid UTF-8 is parsed from the wire or
 assigned to a string field.

 TODO: clarify exactly what kinds of field types this option
 applies to, and update these docs accordingly.

 Proto3 files already perform these checks. Setting the option explicitly to
 false has no effect: it cannot be used to opt proto3 files out of UTF-8
 checks.



ä



ä



ä&


ä)+


ä,=


ä7<
L

çì< Generated classes can be optimized for speed or code size.




ç
D

è"4 Generate complete code for parsing, serialization,




è	


è
G


ê etc.
"/ Use ReflectionOps to implement these methods.





ê



ê
G

ë"7 Generate code using MessageLite and the lite runtime.




ë


ë


í;


í



í



í$


í'(


í):


í49
â

ô"Ó Sets the Go package where structs generated from this .proto will be
 placed. If omitted, the Go package will be derived from the following:
   - The basename of the package import path, if provided.
   - Otherwise, the package statement in the .proto file, if present.
   - Otherwise, the basename of the .proto file, without extension.



ô



ô



ô


ô!
Ô

€;Å Should generic services be generated in each language?  "Generic" services
 are not specific to any particular RPC system.  They are generated by the
 main code generators in each language (without additional plugins).
 Generic services were the only kind of service generation supported by
 early versions of google.protobuf.

 Generic services are now considered deprecated in favor of using plugins
 that generate code specific to your particular RPC system.  Therefore,
 these default to false.  Old code which depends on generic services should
 explicitly set them to true.



€



€



€#


€&(


€):


€49


�=


�



�



�%


�(*


�+<


�6;


	‚;


	‚



	‚


	
‚#


	‚&(


	‚):


	‚49
+

	ƒ" removed php_generic_services



	ƒ


	
ƒ


	ƒ



„"



„!
ó



Š2ä
 Is this file deprecated?
 Depending on the target platform, this can emit Deprecated annotations
 for everything in the file, or it will be completely ignored; in the very
 least, this is a formalization for deprecating files.




Š




Š




Š



Š



Š 1



Š+0


Ž7q Enables the use of arenas for the proto messages in this file. This applies
 only to generated classes for C++.



Ž



Ž



Ž 


Ž#%


Ž&6


Ž15
’


’)ƒ
 Sets the objective c class prefix which is prepended to all objective c
 generated classes from this .proto. There is no default.



’



’



’#


’&(
I


•(; Namespace for generated classes; defaults to the package.




•




•




•"



•%'
‘

›$‚ By default Swift generators will take the proto package and CamelCase it
 replacing '.' with underscore and use that to prefix the types/symbols
 defined. When this options is provided, they will use this value instead
 to prefix the types/symbols defined.



›



›



›


›!#
~

Ÿ(p Sets the php class prefix which is prepended to all php generated classes
 from this .proto. Default is empty.



Ÿ



Ÿ



Ÿ"


Ÿ%'
¾


¤%¯
 Use this option to change the namespace of php generated classes. Default
 is empty. When this option is empty, the package name will be used for
 determining the namespace.



¤



¤



¤


¤"$
Ê


©.»
 Use this option to change the namespace of php generated metadata classes.
 Default is empty. When this option is empty, the proto file name will be
 used for determining the namespace.



©



©



©(


©+-
Â


®$³
 Use this option to change the package of ruby generated classes. Default
 is empty. When this option is not set, the package name will be used for
 determining the ruby package.



®



®



®


®!#
‘

´$‚ Any features defined in the specific edition.
 WARNING: This field should only be used by protobuf plugins or special
 cases like the proto compiler. Other uses are discouraged and
 developers should rely on the protoreflect APIs for their client language.



´



´



´


´!#
”


¸¼„
 Range reserved for first-class custom options defined by the Protobuf
 team. User custom options must use the 1000+ range instead.



¸




¸



¸


¸¼
|

À:n The parser stores options it doesn't recognize here.
 See the documentation for the "Options" section above.



À



À



À3


À69
‡


Äz Clients can define custom options in extensions of this message.
 See the documentation for the "Options" section above.




Ä





Ä




Ä


	Æ


	
Æ


	

Æ


	
Æ

É 



É
Ø
Ü>É Set true to use the old proto1 MessageSet wire format for extensions.
 This is provided for backwards-compatibility with the MessageSet wire
 format.  You should not use this for any other reason:  It's less
 efficient, has fewer features, and is more complicated.

 The message must be defined exactly as follows:
   message Foo {
     option message_set_wire_format = true;
     extensions 4 to max;
   }
 Note that the message cannot have any defined fields; MessageSets only
 have extensions.

 All extensions of your type must be singular messages; e.g. they cannot
 be int32s, enums, or repeated messages.

 Because this is an option, the above two restrictions are not enforced by
 the protocol compiler.


Ü


Ü


Ü'

Ü*+

Ü,=

Ü7<
ë


áFÜ
 Disables the generation of the standard "descriptor()" accessor, which can
 conflict with a field of the same name.  This is meant to make migration
 from proto1 easier; new code should avoid fields named "descriptor".



á



á



á/


á23


á4E


á?D
î

ç1ß
 Is this message deprecated?
 Depending on the target platform, this can emit Deprecated annotations
 for the message, or it will be completely ignored; in the very least,
 this is a formalization for deprecating messages.


ç


ç


ç

ç

ç0

ç*/

	é

	é

	
é

	é

	
é

	

é

	
é

	é

	
é

	é
 
€‘ Whether the message is an automatically generated map entry type for the
 maps field.

 For maps fields:
     map<KeyType, ValueType> map_field = 1;
 The parsed descriptor looks like:
     message MapFieldEntry {
         option map_entry = true;
         optional KeyType key = 1;
         optional ValueType value = 2;
     }
     repeated MapFieldEntry map_field = 1;

 Implementations may choose not to generate the map_entry=true message, but
 use a native map in the target language to hold the keys and values.
 The reflection APIs in such implementations still need to work as
 if the field is a repeated message field.

 NOTE: Do not set the option in .proto files. Always use the maps syntax
 instead. The option should only be implicitly set by the proto compiler
 parser.


€


€


€

€
$
	‚
" javalite_serializable


	‚

	
‚

	‚

	ƒ
" javanano_as_lite


	ƒ

	
ƒ

	ƒ
Ý
�PÎ Enable the legacy handling of JSON field name conflicts.  This lowercases
 and strips underscored from the fields before comparison in proto3 only.
 The new behavior takes `json_name` into account and applies to proto2 as
 well.

 This should only be used as a temporary measure against broken builds due
 to the change in behavior for JSON field name conflicts.

 TODO This is legacy behavior we plan to remove once downstream
 teams have had time to migrate.


�


�


�6

�9;

�<O

�=N
‘
•$‚ Any features defined in the specific edition.
 WARNING: This field should only be used by protobuf plugins or special
 cases like the proto compiler. Other uses are discouraged and
 developers should rely on the protoreflect APIs for their client language.


•


•


•

•!#
’

™„
 Range reserved for first-class custom options defined by the Protobuf
 team. User custom options must use the 1000+ range instead.


™



™


™
O
œ:A The parser stores options it doesn't recognize here. See above.


œ


œ


œ3

œ69
Z
ŸM Clients can define custom options in extensions of this message. See above.



Ÿ




Ÿ



Ÿ

¢Ñ



¢
Â
ªE³ NOTE: ctype is deprecated. Use `features.(pb.cpp).string_type` instead.
 The ctype option instructs the C++ code generator to use a different
 representation of the field than it normally would.  See the specific
 options below.  This option is only implemented to support use of
 [ctype=CORD] and [ctype=STRING] (the default) on non-repeated fields of
 type "bytes" in the open source release.
 TODO: make ctype actually deprecated.


ª


ª


ª

ª

ªD

ª=C

«¸


«

­ Default mode.



­


­

–

µ
… The option [ctype=CORD] may be applied to a non-repeated field of type
 "bytes". It indicates that in C++, the data should be stored in a Cord
 instead of a string.  For very large strings, this may reduce memory
 fragmentation. It may also allow better performance when parsing from a
 Cord, or when parsing with aliasing enabled, as the parsed Cord may then
 alias the original buffer.




µ


µ

·


·

·
Ó

ÀÄ The packed option can be enabled for repeated primitive fields to enable
 a more efficient representation on the wire. Rather than repeatedly
 writing the tag and type for each element, the entire array is encoded as
 a single length-delimited blob. In proto3, only explicit setting it to
 false will avoid using packed encoding.  This option is prohibited in
 Editions, but the `repeated_field_encoding` feature can be used to control
 the behavior.



À



À



À


À
š
Í3‹ The jstype option determines the JavaScript type used for values of the
 field.  The option is permitted only for 64 bit integral and fixed types
 (int64, uint64, sint64, fixed64, sfixed64).  A field with jstype JS_STRING
 is represented as JavaScript string, which avoids loss of precision that
 can happen when a large value is converted to a floating point JavaScript.
 Specifying JS_NUMBER for the jstype causes the generated JavaScript code to
 use the JavaScript "number" type.  The behavior of the default option
 JS_NORMAL is implementation dependent.

 This option is an enum to permit additional types to be added, e.g.
 goog.math.Integer.


Í


Í


Í

Í

Í2

Í(1


Î×



Î
'

Ð Use the default type.




Ð


Ð
)


Ó Use JavaScript strings.





Ó



Ó
)

Ö Use JavaScript numbers.




Ö


Ö
™

ï+Š
 Should this field be parsed lazily?  Lazy applies only to message-type
 fields.  It means that when the outer message is initially parsed, the
 inner message's contents will not be parsed but instead stored in encoded
 form.  The inner message will actually be parsed when it is first accessed.

 This is only a hint.  Implementations are free to choose whether to use
 eager or lazy parsing regardless of the value of this option.  However,
 setting this option true suggests that the protocol author believes that
 using lazy parsing on this field is worth the additional bookkeeping
 overhead typically needed to implement it.

 This option does not affect the public interface of any generated code;
 all method signatures remain the same.  Furthermore, thread-safety of the
 interface is not affected by this option; const methods remain safe to
 call from multiple threads concurrently, while non-const methods continue
 to require exclusive access.

 Note that lazy message fields are still eagerly verified to check
 ill-formed wireformat or missing required fields. Calling IsInitialized()
 on the outer message would fail if the inner message has missing required
 fields. Failed verification would result in parsing failure (except when
 uninitialized messages are acceptable).


ï


ï


ï

ï

ï*

ï$)
¯

ô7 
 unverified_lazy does no correctness checks on the byte stream. This should
 only be used where lazy with verification is prohibitive for performance
 reasons.


ô


ô


ô

ô"$

ô%6

ô05
è

ú1Ù
 Is this field deprecated?
 Depending on the target platform, this can emit Deprecated annotations
 for accessors, or it will be completely ignored; in the very least, this
 is a formalization for deprecating fields.


ú


ú


ú

ú

ú0

ú*/
X
þ?J DEPRECATED. DO NOT USE!
 For Google-internal migration only. Do not use.


þ


þ


þ

þ

þ>

þ%*

þ,=
—

‚4ˆ
 Indicate that the field value should not be printed out when using debug
 formats, e.g. when the field contains sensitive credentials.


‚


‚


‚

‚!

‚"3

‚-2
Y
…‰I If set to RETENTION_SOURCE, the option will be omitted from the binary.



…

†


†

†


‡



‡


‡

ˆ


ˆ

ˆ

‹*

‹


‹


‹$

‹')
Ã

�›²
 This indicates the types of entities that the field may apply to when used
 as an option. If it is unset, then the field may be freely used as an
 option on any kind of entity.



�

‘


‘

‘


’



’


’

“$


“

“"#

”


”

”

•


•

•

–


–

–

—


—

—

˜


˜

˜

™


™

™

	š

	
š

	š

	�)

	�


	�

	
�#

	�&(

٢


Ÿ


 !

 

 



 

  
"

¡" Textproto value.



¡


¡




¡


¡


£0


£



£



£*


£-/
‘
©$‚ Any features defined in the specific edition.
 WARNING: This field should only be used by protobuf plugins or special
 cases like the proto compiler. Other uses are discouraged and
 developers should rely on the protoreflect APIs for their client language.


©


©


©

©!#
D

¬Â4 Information about the support window of a feature.




¬

Ô


°,Ã
 The edition that this feature was first available in.  In editions
 earlier than this one, the default assigned to EDITION_LEGACY will be
 used, and proto files will not be able to override it.



°


°




°'


°*+
w


´,g The edition this feature becomes deprecated in.  Using this after this
 edition may trigger warnings.




´



´





´'



´*+
v

¸,f The deprecation warning text if this feature is used after the edition it
 was marked deprecated in.



¸


¸




¸'


¸*+
¾


½)­
 The edition this feature is no longer available in.  In editions after
 this one, the last default assigned will be used, and proto files will
 not be able to override it.



½


½




½$


½'(
f

Á&V The removal error text if this feature is used after the edition it was
 removed in.



Á


Á




Á!


Á$%

Ã/

Ã


Ã


Ã)

Ã,.
’

Ç„
 Range reserved for first-class custom options defined by the Protobuf
 team. User custom options must use the 1000+ range instead.


Ç



Ç


Ç
O

Ê:A The parser stores options it doesn't recognize here. See above.



Ê



Ê



Ê3


Ê69
Z
ÍM Clients can define custom options in extensions of this message. See above.



Í




Í



Í

	Ï
" removed jtype


	Ï

	
Ï

	Ï
9
	Ð", reserve target, target_obsolete_do_not_use


	
Ð

	

Ð

	
Ð


Óã




Ó
‘

Ø#‚ Any features defined in the specific edition.
 WARNING: This field should only be used by protobuf plugins or special
 cases like the proto compiler. Other uses are discouraged and
 developers should rely on the protoreflect APIs for their client language.



Ø



Ø



Ø


Ø!"
’


Ü„
 Range reserved for first-class custom options defined by the Protobuf
 team. User custom options must use the 1000+ range instead.



Ü




Ü



Ü
O


ß:A The parser stores options it doesn't recognize here. See above.




ß




ß




ß3



ß69
Z

âM Clients can define custom options in extensions of this message. See above.




â





â




â

åŠ



å
`
é R Set this option to true to allow mapping different tag names to the same
 value.


é


é


é

é
å


ï1Ö
 Is this enum deprecated?
 Depending on the target platform, this can emit Deprecated annotations
 for the enum, or it will be completely ignored; in the very least, this
 is a formalization for deprecating enums.



ï



ï



ï


ï


ï0


ï*/

	ñ
" javanano_as_lite


	ñ

	
ñ

	ñ
È
ùO¹ Enable the legacy handling of JSON field name conflicts.  This lowercases
 and strips underscored from the fields before comparison in proto3 only.
 The new behavior takes `json_name` into account and applies to proto2 as
 well.
 TODO Remove this legacy behavior once downstream teams have
 had time to migrate.


ù


ù


ù6

ù9:

ù;N

ù<M
‘
ÿ#‚ Any features defined in the specific edition.
 WARNING: This field should only be used by protobuf plugins or special
 cases like the proto compiler. Other uses are discouraged and
 developers should rely on the protoreflect APIs for their client language.


ÿ


ÿ


ÿ

ÿ!"
’

ƒ„
 Range reserved for first-class custom options defined by the Protobuf
 team. User custom options must use the 1000+ range instead.


ƒ



ƒ


ƒ
O
†:A The parser stores options it doesn't recognize here. See above.


†


†


†3

†69
Z
‰M Clients can define custom options in extensions of this message. See above.



‰




‰



‰

Ψ



Œ
÷

‘1è
 Is this enum value deprecated?
 Depending on the target platform, this can emit Deprecated annotations
 for the enum value, or it will be completely ignored; in the very least,
 this is a formalization for deprecating enum values.


‘


‘


‘

‘

‘0

‘*/
‘

—#‚ Any features defined in the specific edition.
 WARNING: This field should only be used by protobuf plugins or special
 cases like the proto compiler. Other uses are discouraged and
 developers should rely on the protoreflect APIs for their client language.



—



—



—


—!"
®

œ3Ÿ
 Indicate that fields annotated with this enum value should not be printed
 out when using debug formats, e.g. when the field contains sensitive
 credentials.


œ


œ


œ

œ 

œ!2

œ,1
H
Ÿ;: Information about the support window of a feature value.


Ÿ


Ÿ&


Ÿ'6

Ÿ9:
’

£§‚
 Range reserved for first-class extension options defined by the Protobuf
 team. Custom options must use the 1000+ range instead.


£



£


£

£§
O
ª:A The parser stores options it doesn't recognize here. See above.


ª


ª


ª3

ª69
Z
­M Clients can define custom options in extensions of this message. See above.



­




­



­

°Ì



°
‘
¶$‚ Any features defined in the specific edition.
 WARNING: This field should only be used by protobuf plugins or special
 cases like the proto compiler. Other uses are discouraged and
 developers should rely on the protoreflect APIs for their client language.


¶


¶


¶

¶!#
Ù

Á2ß
 Is this service deprecated?
 Depending on the target platform, this can emit Deprecated annotations
 for the service, or it will be completely ignored; in the very least,
 this is a formalization for deprecating services.
2è
 Note:  Field numbers 1 through 32 are reserved for Google's internal RPC
   framework.  We apologize for hoarding these numbers to ourselves, but
   we were already using them long before we decided to release Protocol
   Buffers.



Á



Á



Á


Á


Á 1


Á+0
’

Å„
 Range reserved for first-class custom options defined by the Protobuf
 team. User custom options must use the 1000+ range instead.


Å



Å


Å
O
È:A The parser stores options it doesn't recognize here. See above.


È


È


È3

È69
Z
ËM Clients can define custom options in extensions of this message. See above.



Ë




Ë



Ë

Îõ



Î
Ö
Ù2Ü
 Is this method deprecated?
 Depending on the target platform, this can emit Deprecated annotations
 for the method, or it will be completely ignored; in the very least,
 this is a formalization for deprecating methods.
2è
 Note:  Field numbers 1 through 32 are reserved for Google's internal RPC
   framework.  We apologize for hoarding these numbers to ourselves, but
   we were already using them long before we decided to release Protocol
   Buffers.


Ù


Ù


Ù

Ù

Ù 1

Ù+0
ð

Þâß
 Is this method side-effect-free (or safe in HTTP parlance), or idempotent,
 or neither? HTTP based RPC implementation may choose GET verb for safe
 methods, and PUT verb for idempotent methods instead of the default POST.



Þ

ß


ß

ß
$

à" implies idempotent




à


à
7
á"' idempotent, but may have side effects



á

á


ãä&


ã



ã



ã-


ã02


ä%


ä$
‘
ê$‚ Any features defined in the specific edition.
 WARNING: This field should only be used by protobuf plugins or special
 cases like the proto compiler. Other uses are discouraged and
 developers should rely on the protoreflect APIs for their client language.


ê


ê


ê

ê!#
’

î„
 Range reserved for first-class custom options defined by the Protobuf
 team. User custom options must use the 1000+ range instead.


î



î


î
O
ñ:A The parser stores options it doesn't recognize here. See above.


ñ


ñ


ñ3

ñ69
Z
ôM Clients can define custom options in extensions of this message. See above.



ô




ô



ô
‹
ý‘
ü A message representing a option the parser does not recognize. This only
 appears in options protos created by the compiler::Parser class.
 DescriptorPool resolves these when building Descriptor objects. Therefore,
 options protos in descriptor objects (e.g. returned by Descriptor::options(),
 or produced by Descriptor::CopyTo()) will never have UninterpretedOptions
 in them.



ý
Ë
ƒ†º The name of the uninterpreted option.  Each string represents a segment in
 a dot-separated name.  is_extension is true iff a segment represents an
 extension (denoted with parentheses in options specs in .proto files).
 E.g.,{ ["foo", false], ["bar.baz", true], ["moo", false] } represents
 "foo.(bar.baz).moo".



ƒ


„"

„

„



„

„ !


…#


…


…




…


…!"

‡

‡


‡


‡

‡
œ


‹'�
 The value of the uninterpreted option, in whatever type the tokenizer
 identified it as during parsing. Exactly one of these should be set.



‹



‹



‹"


‹%&

Œ)

Œ


Œ


Œ$

Œ'(

�(

�


�


�#

�&'

Ž#

Ž


Ž


Ž

Ž!"

�"

�


�


�

� !

�&

�


�


�!

�$%
Û
œ‚

û TODO Enums in C++ gencode (and potentially other languages) are
 not well scoped.  This means that each of the feature enums below can clash
 with each other.  The short names we've chosen maximize call-site
 readability, but leave us very open to this scenario.  A future feature will
 be designed and implemented to handle this, hopefully before we ever hit a
 conflict here.
2O ===================================================================
 Features



œ

�¢


�

ž


ž

ž


Ÿ



Ÿ


Ÿ

 


 

 

¡


¡

¡

£­

£


£


£'

£*+

£,­

¤!

¥


¦

§©

ªE


«E

¬C


¯³



¯


°



°


°



±




±



±


²



²



²



´½


´



´



´


´ !


´"½


µ!


¶



·


¸º


»C



¼A

¿Ã


¿

À(


À#

À&'


Á



Á



Á


Â


Â

Â

ÄÍ

Ä


Ä 


Ä!8

Ä;<

Ä=Í

Å!

Æ


Ç

ÈÊ

ËE


ÌC

ÏÔ


Ï

Ð 


Ð

Ð


Ñ



Ñ



Ñ


Ò


Ò

Ò

Ó

Ó



Ó


Ó


ÕÞ

Õ


Õ


Õ)

Õ,-

Õ.Þ

Ö!

×


Ø

ÙÛ

ÜA


ÝC

àä


à

á!


á

á 


â



â


â

ã


ã

ã

åí

å


å


å+

å./

å0í

æ!

ç


è

éë

ìL

ïó


ï

ð


ð

ð


ñ



ñ	


ñ

ò


ò

ò

ôþ

ô


ô


ô!

ô$%

ô&þ

õ!

ö!


÷

ø

ùû

üO


ýB

€	…	


€	

�	%


�	 

�	#$


‚	



‚	


‚	

ƒ	


ƒ	

ƒ	

„	


„	

„	

†	—	

†	


†	


†	2

†	56

†	7—	

‡	 

ˆ	


‰	)

Š	!

‹	

Œ	

�	

Ž	$

�	!

�	 

‘	“	

”	I


•	D

–	D

™	¬	


™	


š	ª	


š		 

›	,

	
›	'

	›	*+
N

ž	< Default pre-EDITION_2024, all UNSET visibility are export.


	

ž	

	
ž	
U
¡	C All top-level symbols default to export, nested default to local.


	
¡	

	¡	
1
¤	 All symbols default to local.


	
¤	

	¤	
É

©	¶
 All symbols local by default. Nested types cannot be exported.
 With special case caveat for message { enum {} reserved 1 to max; }
 This is the recommended setting for new protos.


	
©	

	©	

	«	

	«	


	
«	


	«	

­	¶	

­	


­	4


­	5N

®	

®	¶	

¯	$

°	"

±	³		

´	K


µ	O


¸	Æ	



¸	



¹	Å	



¹		


º	

	

º	

	
º	
�


À	$î
 Default pre-EDITION_2026: there are no limit enforcement at the protoc
 level. Practical limits still exist, but they will tend to fail while
 compiling protoc-generated code, and these limits tend to be language
 or toolchain specific.


	


À	

	

À	"#
Ÿ


Ä	Œ
 A set of limits enforced by Edition 2026 by default. For a detailed
 list of all the limits please consult the Edition 2026 documentation.


	

Ä	

	
Ä	

Ç	Õ	

Ç	


Ç	0


Ç	1E

Ç	HI

Ç	JÕ	

È	 

É	


Ê	!

Ë	

Ì	

Í	Ï	

Ð	Ó	


Ô	K

	×	

	×	

	
×	

	×	

Ù	þ	

Ù	



Ù	


Ù	

Ù	þ	
#
€
" For internal testing



€





€




€

:
�
"- for https://github.com/bufbuild/protobuf-es


�




�



�


¬
ˆ
¢

� A compiled specification for the defaults of a set of features.  These
 messages are generated from FeatureSet extensions and can be used to seed
 feature resolution. The resolution with this object becomes a simple search
 for the closest matching edition, followed by proto merges.



ˆ

°
�
˜
Ÿ A map from every known edition with a unique set of defaults to its
 defaults. Not all editions may be contained here.  For a given edition,
 the defaults at the closest matching edition ordered at or before it should
 be used.  This field must be in strict ascending order by edition.



�

"

Ž
!

Ž


Ž




Ž


Ž
 
N

‘
1> Defaults of features that can be overridden in this edition.



‘



‘





‘
,


‘
/0
P
”
+@ Defaults of features that can't be overridden in this edition.


”


”




”
&

”
)*

	–


	–



	
–



	–



	
–


	

–


	
–



—



—



™
1

™



™
#


™
$,

™
/0
‚


�
't The minimum supported edition (inclusive) when this was constructed.
 Editions before this will not have defaults.



�




�




�
"


�
%&
†

¡
'x The maximum known edition (inclusive) when this was constructed. Editions
 after this will not have reliable defaults.


¡



¡



¡
"

¡
%&
Ú

©
±
j Encapsulates information about the original source file from which a
 FileDescriptorProto was generated.
2` ===================================================================
 Optional source code info



©

‚
Õ
!ó A Location identifies a piece of source code in a .proto file which
 corresponds to a particular definition.  This information is intended
 to be useful to IDEs, code indexers, documentation generators, and similar
 tools.

 For example, say we have a file like:
   message Foo {
     optional string foo = 1;
   }
 Let's look at just the field definition:
   optional string foo = 1;
   ^       ^^     ^^  ^  ^^^
   a       bc     de  f  ghi
 We have the following locations:
   span   path               represents
   [a,i)  [ 4, 0, 2, 0 ]     The whole field definition.
   [a,b)  [ 4, 0, 2, 0, 4 ]  The label (optional).
   [c,d)  [ 4, 0, 2, 0, 5 ]  The type (string).
   [e,f)  [ 4, 0, 2, 0, 1 ]  The name (foo).
   [g,h)  [ 4, 0, 2, 0, 3 ]  The number (1).

 Notes:
 - A location may refer to a repeated field itself (i.e. not to any
   particular index within it).  This is used whenever a set of elements are
   logically enclosed in a single code segment.  For example, an entire
   extend block (possibly containing multiple extension definitions) will
   have an outer location whose path refers to the "extensions" repeated
   field without an index.
 - Multiple locations may have the same path.  This happens when a single
   logical declaration is spread out across multiple places.  The most
   obvious example is the "extend" block again -- there may be multiple
   extend blocks in the same scope, each of which will have the same path.
 - A location's span is not always a subset of its parent's span.  For
   example, the "extendee" of an extension declaration appears at the
   beginning of the "extend" block and is shared by all extensions within
   the block.
 - Just because a location's span is a subset of some other location's span
   does not mean that it is a descendant.  For example, a "group" defines
   both a type and a field in a single declaration.  Thus, the locations
   corresponding to the type and field and their components will overlap.
 - Code which tries to interpret locations should probably be designed to
   ignore those that it doesn't understand, as more types of locations could
   be recorded in the future.


Õ



Õ



Õ


Õ
 

Ö
©


Ö


Š
î
,ù Identifies which part of the FileDescriptorProto was defined at this
 location.

 Each element is a field number or an index.  They form a path from
 the root FileDescriptorProto to the place where the definition appears.
 For example, this path:
   [ 4, 3, 2, 7, 1 ]
 refers to:
   file.message_type(3)  // 4, 3
       .field(7)         // 2, 7
       .name()           // 1
 This is because FileDescriptorProto.message_type has field number 4:
   repeated DescriptorProto message_type = 4;
 and DescriptorProto.field has field number 2:
   repeated FieldDescriptorProto field = 2;
 and FieldDescriptorProto.name has field number 1:
   optional string name = 1;

 Thus, the above path gives the location of a field name.  If we removed
 the last element:
   [ 4, 3, 2, 7 ]
 this path refers to the whole field declaration (from the beginning
 of the label to the terminating semicolon).


î


î




î


î


î
+

î
*
Ò

õ
,Á Always has exactly three or four elements: start line, start column,
 end line (optional, otherwise assumed same as start line), end column.
 These are packed into a single field for efficiency.  Note that line
 and column numbers are zero-based -- typically you will want to add
 1 to each before displaying to a user.



õ



õ





õ



õ



õ
+


õ
*
¥
¦)” If this SourceCodeInfo represents a complete declaration, these are any
 comments appearing before and after the declaration which appear to be
 attached to the declaration.

 A series of line comments appearing on consecutive lines, with no other
 tokens appearing on those lines, will be treated as a single comment.

 leading_detached_comments will keep paragraphs of comments that appear
 before (but not connected to) the current element. Each paragraph,
 separated by empty lines, will be one comment element in the repeated
 field.

 Only the comment content is provided; comment markers (e.g. //) are
 stripped out.  For block comments, leading whitespace and an asterisk
 will be stripped from the beginning of each line other than the first.
 Newlines are included in the output.

 Examples:

   optional int32 foo = 1;  // Comment attached to foo.
   // Comment attached to bar.
   optional int32 bar = 2;

   optional string baz = 3;
   // Comment attached to baz.
   // Another line attached to baz.

   // Comment attached to moo.
   //
   // Another line attached to moo.
   optional double moo = 4;

   // Detached comment for corge. This is not leading or trailing comments
   // to moo or corge because there are blank lines separating it from
   // both.

   // Detached comment for corge paragraph 2.

   optional string corge = 5;
   /* Block comment attached
    * to corge.  Leading asterisks
    * will be removed. */
   /* Block comment attached to
    * grault. */
   optional int32 grault = 6;

   // ignored detached comments.


¦

¦



¦$

¦'(

§*

§

§



§%

§()

¨2

¨

¨



¨-

¨01
(
¬° Extensions for tooling.


¬



¬


¬


¬°
î

¶×
ß
 Describes the relationship between generated code and its original source
 file. A GeneratedCodeInfo message is associated with only one generated
 source file, but may contain references to different source .proto files.



¶
x
¹%j An Annotation connects some span of text in generated code to an element
 of its generating .proto file.


¹


¹


¹ 

¹#$

ºÖ


º

�

½, Identifies the element in the original source .proto file. This field
 is formatted the same as SourceCodeInfo.Location.path.


½

½



½

½

½+

½*
O

À$? Identifies the filesystem path to the original source .proto.



À


À




À


À"#
w
Äg Identifies the starting offset in bytes in the generated code
 that relates to the identified object.


Ä

Ä



Ä

Ä
Û

ÉÊ
 Identifies the ending offset in bytes in the generated code that
 relates to the identified object. The end offset should be one past
 the last relevant byte (so the length of the text = end - begin).


É

É



É

É
j
ÍÔX Represents the identified object's effect on the element in the original
 .proto file.



Í	
F
Ï4 There is no effect or the effect is indescribable.


	
Ï


	Ï

<

Ñ* The element is set or otherwise mutated.


	

Ñ	

	
Ñ
8
Ó& An alias to the element is returned.


	
Ó

	Ó

Õ#

Õ

Õ



Õ

Õ!"
Ø

Þâ
É Describes the 'visibility' of a symbol with respect to the proto import
 system. Symbols can only be imported when the visibility rules do not prevent
 it (ex: local symbols cannot be imported).  Visibility modifiers can only set
 on `message` and `enum` as they are the only types available to be referenced
 from other files.




Þ


ß



ß


ß



à




à



à


á



á


áŠ
Žè
&proto/google/protobuf/descriptor.protogoogle.protobuf"Ê

FileDescriptorSet8
file
 (2$.google.protobuf.FileDescriptorProtoRfile*{€ìÊÿ
�ìÊÿ
mk€ìÊÿ
4.buf.descriptor.v1.buf_file_descriptor_set_extension-.buf.descriptor.v1.FileDescriptorSetExtension"Å
FileDescriptorProto
name
 
(	Rname
package 
(	Rpackage

dependency (	R
dependency+
public_dependency
 (RpublicDependency'
weak_dependency (RweakDependency+
option_dependency (	RoptionDependencyC
message_type (2 .google.protobuf.DescriptorProtoRmessageTypeA
	enum_type (2$.google.protobuf.EnumDescriptorProtoRenumTypeA
service (2'.google.protobuf.ServiceDescriptorProtoRserviceC
	extension (2%.google.protobuf.FieldDescriptorProtoR	extension6
options 
(2.google.protobuf.FileOptionsRoptionsI
source_code_info	 
(2.google.protobuf.SourceCodeInfoRsourceCodeInfo
syntax 
(	Rsyntax2
edition 
(2.google.protobuf.EditionRedition"ü
DescriptorProto
name
 
(	Rname;
field (2%.google.protobuf.FieldDescriptorProtoRfieldC
	extension (2%.google.protobuf.FieldDescriptorProtoR	extensionA
nested_type (2 .google.protobuf.DescriptorProtoR
nestedTypeA
	enum_type (2$.google.protobuf.EnumDescriptorProtoRenumTypeX
extension_range (2/.google.protobuf.DescriptorProto.ExtensionRangeRextensionRangeD

oneof_decl (2%.google.protobuf.OneofDescriptorProtoR	oneofDecl9
options 
(2.google.protobuf.MessageOptionsRoptionsU
reserved_range	 (2..google.protobuf.DescriptorProto.ReservedRangeR
reservedRange#

reserved_name
 (	RreservedNameA

visibility 
(2!.google.protobuf.SymbolVisibilityR
visibilityz
ExtensionRange
start
 
(Rstart
end 
(Rend@
options 
(2&.google.protobuf.ExtensionRangeOptionsRoptions7

ReservedRange
start
 
(Rstart
end 
(Rend"Ô
ExtensionRangeOptionsX
uninterpreted_optionç (2$.google.protobuf.UninterpretedOptionRuninterpretedOptionY
declaration (22.google.protobuf.ExtensionRangeOptions.DeclarationBˆ
Rdeclaration7
features2 
(2.google.protobuf.FeatureSetRfeaturesm
verification 
(28.google.protobuf.ExtensionRangeOptions.VerificationState:
UNVERIFIEDBˆ
Rverification”

Declaration
number
 
(Rnumber
	full_name 
(	RfullName
type 
(	Rtype
reserved 
(Rreserved
repeated 
(RrepeatedJ"4
VerificationState
DECLARATION

UNVERIFIED
*Þç*	耀€€"Á
FieldDescriptorProto
name
 
(	Rname
number 
(RnumberA
label 
(2+.google.protobuf.FieldDescriptorProto.LabelRlabel>
type 
(2*.google.protobuf.FieldDescriptorProto.TypeRtype
	type_name 
(	RtypeName
extendee 
(	Rextendee#

default_value 
(	RdefaultValue
oneof_index	 
(R
oneofIndex
	json_name
 
(	RjsonName7
options 
(2.google.protobuf.FieldOptionsRoptions'
proto3_optional 
(Rproto3Optional"¶
Type
TYPE_DOUBLE


TYPE_FLOAT

TYPE_INT64
TYPE_UINT64

TYPE_INT32
TYPE_FIXED64
TYPE_FIXED32
	TYPE_BOOL
TYPE_STRING	

TYPE_GROUP

TYPE_MESSAGE

TYPE_BYTES
TYPE_UINT32

	TYPE_ENUM

TYPE_SFIXED32

TYPE_SFIXED64
TYPE_SINT32
TYPE_SINT64"C
Label
LABEL_OPTIONAL

LABEL_REPEATED
LABEL_REQUIRED"c
OneofDescriptorProto
name
 
(	Rname7
options 
(2.google.protobuf.OneofOptionsRoptions"¦
EnumDescriptorProto
name
 
(	Rname?
value (2).google.protobuf.EnumValueDescriptorProtoRvalue6
options 
(2.google.protobuf.EnumOptionsRoptions]
reserved_range (26.google.protobuf.EnumDescriptorProto.EnumReservedRangeR
reservedRange#

reserved_name (	RreservedNameA

visibility 
(2!.google.protobuf.SymbolVisibilityR
visibility;
EnumReservedRange
start
 
(Rstart
end 
(Rend"ƒ

EnumValueDescriptorProto
name
 
(	Rname
number 
(Rnumber;
options 
(2!.google.protobuf.EnumValueOptionsRoptions"µ

ServiceDescriptorProto
name
 
(	Rname>
method (2&.google.protobuf.MethodDescriptorProtoRmethod9
options 
(2.google.protobuf.ServiceOptionsRoptionsJRstream"‰
MethodDescriptorProto
name
 
(	Rname

input_type 
(	R	inputType
output_type 
(	R
outputType8
options 
(2.google.protobuf.MethodOptionsRoptions0
client_streaming 
(:falseRclientStreaming0
server_streaming 
(:falseRserverStreaming"¨
FileOptions!
java_package
 
(	RjavaPackage0
java_outer_classname 
(	RjavaOuterClassnameù

java_multiple_files
 
(:falseBÁ
²
½
æ é*´
This behavior is enabled by default in editions 2024 and above. To disable it, you can set `features.(pb.java).nest_in_file_class = YES` on individual messages, enums, or services.RjavaMultipleFilesD
java_generate_equals_and_hash 
(B
RjavaGenerateEqualsAndHash:
java_string_check_utf8 
(:falseRjavaStringCheckUtf8S
optimize_for	 
(2).google.protobuf.FileOptions.OptimizeMode:SPEEDRoptimizeFor

go_package 
(	R	goPackage5
cc_generic_services 
(:falseRccGenericServices9
java_generic_services 
(:falseRjavaGenericServices5
py_generic_services 
(:falseRpyGenericServices%

deprecated 
(:falseR
deprecated.
cc_enable_arenas 
(:trueRccEnableArenas*
objc_class_prefix$ 
(	RobjcClassPrefix)
csharp_namespace% 
(	RcsharpNamespace!
swift_prefix' 
(	RswiftPrefix(
php_class_prefix( 
(	RphpClassPrefix#

php_namespace) 
(	RphpNamespace4
php_metadata_namespace, 
(	RphpMetadataNamespace!
ruby_package- 
(	RrubyPackage7
features2 
(2.google.protobuf.FeatureSetRfeaturesX
uninterpreted_optionç (2$.google.protobuf.UninterpretedOptionRuninterpretedOption":
OptimizeMode	
SPEED

	CODE_SIZE
LITE_RUNTIME*4Þç,*Þ.pb.file.cpp.pb.file.CppFileOptions*	耀€€J*+J&'Rphp_generic_services"ü
MessageOptions<
message_set_wire_format
 
(:falseRmessageSetWireFormatL
no_standard_descriptor_accessor 
(:falseRnoStandardDescriptorAccessor%

deprecated 
(:falseR
deprecated
	map_entry 
(RmapEntryV
&deprecated_legacy_json_field_conflicts 
(B
R"deprecatedLegacyJsonFieldConflicts7
features 
(2.google.protobuf.FeatureSetRfeaturesX
uninterpreted_optionç (2$.google.protobuf.UninterpretedOptionRuninterpretedOption*Þç*	耀€€JJJJ	J	
"Î
FieldOptionsA
ctype
 
(2#.google.protobuf.FieldOptions.CType:STRINGRctype
packed 
(RpackedG
jstype 
(2$.google.protobuf.FieldOptions.JSType:	JS_NORMALRjstype
lazy 
(:falseRlazy.
unverified_lazy 
(:falseRunverifiedLazy%

deprecated 
(:falseR
deprecated
weak
 
(:falseB
Rweak(
debug_redact 
(:falseRdebugRedactK
	retention 
(2-.google.protobuf.FieldOptions.OptionRetentionR	retentionH
targets (2..google.protobuf.FieldOptions.OptionTargetTypeRtargetsW
edition_defaults (2,.google.protobuf.FieldOptions.EditionDefaultReditionDefaults7
features 
(2.google.protobuf.FeatureSetRfeaturesU
feature_support 
(2,.google.protobuf.FieldOptions.FeatureSupportRfeatureSupportX
uninterpreted_optionç (2$.google.protobuf.UninterpretedOptionRuninterpretedOptionZ
EditionDefault2
edition 
(2.google.protobuf.EditionRedition
value 
(	Rvalue»
FeatureSupportG
edition_introduced
 
(2.google.protobuf.EditionReditionIntroducedG
edition_deprecated 
(2.google.protobuf.EditionReditionDeprecated/
deprecation_warning 
(	RdeprecationWarningA
edition_removed 
(2.google.protobuf.EditionReditionRemoved#

removal_error 
(	RremovalError"/
CType

STRING
CORD

STRING_PIECE"5
JSType
	JS_NORMAL
	JS_STRING

	JS_NUMBER"U
OptionRetention
RETENTION_UNKNOWN
RETENTION_RUNTIME

RETENTION_SOURCE"Œ
OptionTargetType
TARGET_TYPE_UNKNOWN
TARGET_TYPE_FILE

TARGET_TYPE_EXTENSION_RANGE
TARGET_TYPE_MESSAGE
TARGET_TYPE_FIELD
TARGET_TYPE_ONEOF
TARGET_TYPE_ENUM
TARGET_TYPE_ENUM_ENTRY
TARGET_TYPE_SERVICE
TARGET_TYPE_METHOD	*Þç*	耀€€JJ"´

OneofOptions7
features
 
(2.google.protobuf.FeatureSetRfeaturesX
uninterpreted_optionç (2$.google.protobuf.UninterpretedOptionRuninterpretedOption*Þç*	耀€€"Ù
EnumOptions
allow_alias 
(R
allowAlias%

deprecated 
(:falseR
deprecatedV
&deprecated_legacy_json_field_conflicts 
(B
R"deprecatedLegacyJsonFieldConflicts7
features 
(2.google.protobuf.FeatureSetRfeaturesX
uninterpreted_optionç (2$.google.protobuf.UninterpretedOptionRuninterpretedOption*Þç*	耀€€J"Ÿ
EnumValueOptions%

deprecated
 
(:falseR
deprecated7
features 
(2.google.protobuf.FeatureSetRfeatures(
debug_redact 
(:falseRdebugRedactU
feature_support 
(2,.google.protobuf.FieldOptions.FeatureSupportRfeatureSupportX
uninterpreted_optionç (2$.google.protobuf.UninterpretedOptionRuninterpretedOption*EÞç=;æ.pb.enumvalue.json".pb.enumvalue.JsonEnumValueOptions*	耀€€"Ý

ServiceOptions7
features" 
(2.google.protobuf.FeatureSetRfeatures%

deprecated! 
(:falseR
deprecatedX
uninterpreted_optionç (2$.google.protobuf.UninterpretedOptionRuninterpretedOption*Þç*	耀€€"¡

MethodOptions%

deprecated! 
(:falseR
deprecatedq
idempotency_level" 
(2/.google.protobuf.MethodOptions.IdempotencyLevel:IDEMPOTENCY_UNKNOWNRidempotencyLevel7
features# 
(2.google.protobuf.FeatureSetRfeaturesX
uninterpreted_optionç (2$.google.protobuf.UninterpretedOptionRuninterpretedOption"P
IdempotencyLevel
IDEMPOTENCY_UNKNOWN
NO_SIDE_EFFECTS


IDEMPOTENT*Þç*	耀€€"š
UninterpretedOptionA
name (2-.google.protobuf.UninterpretedOption.NamePartRname)
identifier_value 
(	RidentifierValue,
positive_int_value 
(RpositiveIntValue,
negative_int_value 
(RnegativeIntValue!
double_value 
(
RdoubleValue!
string_value 
(RstringValue'
aggregate_value 
(	RaggregateValueJ
NamePart
	name_part
 (	RnamePart!
is_extension (RisExtension"¦

FeatureSet‘

field_presence
 
(2).google.protobuf.FeatureSet.FieldPresenceB?ˆ

˜
˜

¢

EXPLICIT„¢

IMPLICITç¢

EXPLICITè²
èR
fieldPresencel
	enum_type 
(2$.google.protobuf.FeatureSet.EnumTypeB)ˆ

˜
˜

¢
CLOSED„¢
	OPENç²
èRenumType˜

repeated_field_encoding 
(21.google.protobuf.FeatureSet.RepeatedFieldEncodingB-ˆ

˜
˜

¢

EXPANDED„¢
PACKEDç²
èRrepeatedFieldEncoding~
utf8_validation 
(2*.google.protobuf.FeatureSet.Utf8ValidationB)ˆ

˜
˜

¢
	NONE„¢
VERIFYç²
èRutf8Validation~
message_encoding 
(2+.google.protobuf.FeatureSet.MessageEncodingB&ˆ

˜
˜

¢
LENGTH_PREFIXED„²
èRmessageEncoding‚

json_format 
(2&.google.protobuf.FeatureSet.JsonFormatB9ˆ

˜
˜
˜

¢
LEGACY_BEST_EFFORT„¢

ALLOWç²
èR
jsonFormat¼

enforce_naming_style 
(2..google.protobuf.FeatureSet.EnforceNamingStyleBZˆ
˜

˜
˜
˜
˜
˜
˜
˜
˜
	¢
STYLE_LEGACY„¢
	STYLE2024é¢
	STYLE2026ê²
éRenforceNamingStyle¹

default_symbol_visibility 
(2E.google.protobuf.FeatureSet.VisibilityFeature.DefaultSymbolVisibilityB6ˆ
˜

¢

EXPORT_ALL„¢
EXPORT_TOP_LEVELé²
éRdefaultSymbolVisibilityÃ

enforce_proto_limits	 
(2A.google.protobuf.FeatureSet.ProtoLimitsFeature.EnforceProtoLimitsBNˆ
˜
˜
˜
˜
¢
LEGACY_NO_EXPLICIT_LIMITS„¢
PROTO_LIMITS2026ê²
êRenforceProtoLimits¡

VisibilityFeature"�

DefaultSymbolVisibility%
!DEFAULT_SYMBOL_VISIBILITY_UNKNOWN

EXPORT_ALL

EXPORT_TOP_LEVEL
	LOCAL_ALL

STRICTJ
€€€€y
ProtoLimitsFeature"c
EnforceProtoLimits
PROTO_LIMITS_UNKNOWN
LEGACY_NO_EXPLICIT_LIMITS

PROTO_LIMITS2026"\

FieldPresence
FIELD_PRESENCE_UNKNOWN
EXPLICIT

IMPLICIT
LEGACY_REQUIRED"7
EnumType
ENUM_TYPE_UNKNOWN
OPEN


CLOSED"V
RepeatedFieldEncoding#
REPEATED_FIELD_ENCODING_UNKNOWN

PACKED

EXPANDED"I
Utf8Validation
UTF8_VALIDATION_UNKNOWN

VERIFY
NONE"

"S
MessageEncoding
MESSAGE_ENCODING_UNKNOWN
LENGTH_PREFIXED

	DELIMITED"H

JsonFormat
JSON_FORMAT_UNKNOWN	
ALLOW

LEGACY_BEST_EFFORT"f
EnforceNamingStyle 
ENFORCE_NAMING_STYLE_UNKNOWN
	STYLE2024

STYLE_LEGACY
	STYLE2026*¼è‹N³è.pb.cpp.pb.CppFeaturesé.pb.java.pb.JavaFeaturesê.pb.go.pb.GoFeatures#ë
.pb.python.pb.PythonFeatures#ì
.pb.csharp.pb.CSharpFeatures5Ì.imp.impress_feature_set.imp.ImpressFeatureSet.…N.pb.java_mutable.pb.JavaMutableFeatures#†N
.pb.proto1.pb.Proto1Features*‹N�N*�N‘NJçè"ï
FeatureSetDefaultsX
defaults
 (2<.google.protobuf.FeatureSetDefaults.FeatureSetEditionDefaultRdefaultsA
minimum_edition 
(2.google.protobuf.EditionRminimumEditionA
maximum_edition 
(2.google.protobuf.EditionRmaximumEditionø

FeatureSetEditionDefault2
edition 
(2.google.protobuf.EditionReditionN
overridable_features 
(2.google.protobuf.FeatureSetRoverridableFeaturesB
fixed_features 
(2.google.protobuf.FeatureSetR
fixedFeaturesJ
JRfeatures"ž
SourceCodeInfoD
location
 (2(.google.protobuf.SourceCodeInfo.LocationRlocationÎ

Location
path
 (B
Rpath
span (B
Rspan)
leading_comments 
(	RleadingComments+
trailing_comments 
(	RtrailingComments:
leading_detached_comments (	RleadingDetachedComments*u€ìÊÿ
�ìÊÿ
ge€ìÊÿ
1.buf.descriptor.v1.buf_source_code_info_extension*.buf.descriptor.v1.SourceCodeInfoExtension"Ð
GeneratedCodeInfoM

annotation
 (2-.google.protobuf.GeneratedCodeInfo.AnnotationR
annotationë


Annotation
path
 (B
Rpath
source_file 
(	R
sourceFile
begin 
(Rbegin
end 
(RendR
semantic 
(26.google.protobuf.GeneratedCodeInfo.Annotation.SemanticRsemantic"(
Semantic
NONE
SET
	
ALIAS*Ñ
Edition
EDITION_UNKNOWN
EDITION_LEGACY„
EDITION_PROTO2æ
EDITION_PROTO3ç
EDITION_2023è
EDITION_2024é
EDITION_2026ê
EDITION_UNSTABLE�N
EDITION_1_TEST_ONLY

EDITION_2_TEST_ONLY
EDITION_99997_TEST_ONLY��
EDITION_99998_TEST_ONLYž�
EDITION_99999_TEST_ONLYŸ�
EDITION_MAXÿÿÿÿ*U
SymbolVisibility
VISIBILITY_UNSET
VISIBILITY_LOCAL

VISIBILITY_EXPORTB~
com.google.protobufBDescriptorProtosH
Z-google.golang.org/protobuf/types/descriptorpbø

¢GPBªGoogle.Protobuf.ReflectionJ¿ö
â

ò

2‰ Protocol Buffers - Google's data interchange format
 Copyright 2008 Google LLC.  All rights reserved.

 Use of this source code is governed by a BSD-style
 license that can be found in the LICENSE file or at
 https://developers.google.com/open-source/licenses/bsd
2Û Author: kenton@google.com (Kenton Varda)
  Based on original Protocol Buffers design by
  Sanjay Ghemawat, Jeff Dean, and others.

 The messages in this file describe the definitions found in .proto files.
 A valid .proto file can be translated directly to a FileDescriptorProto
 without any other information (e.g. without reading its imports).






D
	
D


,
	

,


1
	
1


7
	
%7


!
	
$!



	





	t descriptor.proto must be optimized for speed because reflection-based
 algorithms don't work during bootstrapping.

j
 )
^ The protocol compiler can output a FileDescriptorSet containing the .proto
 files it parses.




 

!(

!


!


!#

!&'
&
$( Extensions for tooling.


$



$


$


$(

$(
-
,Q
! The full set of known editions.




,
:
.- A placeholder for an unknown edition value.



.

.
™


2‹
 A placeholder edition for specifying default behaviors *before* a feature
 was first introduced.  This is effectively an "infinite past".




2


2
‚
8ô
 Legacy syntax "editions".  These pre-date editions, but behave much like
 distinct editions.  These can't be used to specify the edition of proto
 files, but feature definitions must supply proto2/proto3 defaults for
 backwards compatibility.



8

8

9


9

9
¯

>¡
 Editions that have been released.  The specific values are arbitrary and
 should not be depended on, but they will always be time-ordered for easy
 comparison.



>

>

?


?

?

@


@

@
U
CH A placeholder edition for developing and testing unscheduled features.



C

C
}
Gp Placeholder editions for testing feature resolution.  These should not be
 used or relied on outside of tests.



G

G

	H

	
H

	H


I"



I


I!

J"


J

J!

K"


K

K!
¸


Pª
 Placeholder for specifying unbounded edition support.  This should only
 ever be used by plugins that can expect to never require any changes to
 support a new edition.




P


P
0

T€

# Describes a complete .proto file.





T
9

U", file name, relative to root of source tree



U



U



U


U
*


V" e.g. "foo", "foo.bar", etc.




V




V




V



V
4

Y!' Names of files imported by this file.



Y



Y



Y


Y 
Q

[(D Indexes of the public imported files in the dependency list above.



[



[



["


[%'
z

^&m Indexes of the weak imported files in the dependency list.
 For Google-internal migration only. Do not use.



^



^



^ 


^#%
Ÿ


b)‘
 Names of files imported by this file purely for the purpose of providing
 option extensions. These are excluded from the dependency list above.



b



b



b#


b&(
6

e,) All top-level definitions in this file.



e



e



e'


e*+


f-


f



f



f(


f+,


g.


g



g!



g")


g,-


	h.


	h



	h


	
h )


	h,-



j#



j




j




j



j!"
ô


p/æ
 This field contains optional information about the original source code.
 You may safely remove this entire field without harming runtime
 functionality of the descriptors -- the information is needed only by
 development tools.



p



p



p*


p-.
ø

yê The syntax of the proto file.
 The supported values are "proto2", "proto3", and "editions".

 If `edition` is present, this value must be "editions".
 WARNING: This field should only be used by protobuf plugins or special
 cases like the proto compiler. Other uses are discouraged and
 developers should rely on the protoreflect APIs for their client language.



y



y



y


y
�


 ó
 The edition of the proto file.
 WARNING: This field should only be used by protobuf plugins or special
 cases like the proto compiler. Other uses are discouraged and
 developers should rely on the protoreflect APIs for their client language.



















)
ƒ
¦

 Describes a message type.



ƒ


„


„



„



„


„



†
*


†




†




†
 %


†
()

‡
.

‡



‡



‡
 )

‡
,-

‰
+

‰



‰



‰
&

‰
)*

Š
-

Š



Š



Š
(

Š
+,

Œ
‘



Œ



�
" Inclusive.


�


�




�


�



Ž
" Exclusive.



Ž



Ž





Ž



Ž


�
/

�


�

"


�
#*

�
-.

’
.

’



’



’
)

’
,-

”
/

”



”



”
 *

”
-.

–
&

–



–



–
!

–
$%
¬


›
ž
›
 Range of reserved tag numbers. Reserved tag numbers may not be used by
 fields or extension ranges in the same message. Reserved ranges may
 not overlap.




›




œ
" Inclusive.



œ



œ





œ



œ




�
" Exclusive.




�




�






�




�


Ÿ
,

Ÿ



Ÿ



Ÿ
'

Ÿ
*+
ƒ

	¢
%u Reserved field names, which may not be used by fields in the same message.
 A given name may only be reserved once.


	¢



	¢


	
¢


	¢
"$
C

¥
,5 Support for `export` and `local` keywords on enums.



¥




¥




¥
&


¥
)+

¨
ß




¨

’

«
„
 Range reserved for first-class custom options defined by the Protobuf
 team. User custom options must use the 1000+ range instead.


«




«



«

O
­
:A The parser stores options it doesn't recognize here. See above.


­



­



­
3

­
69

¯
Æ



¯


K
±
; The extension number declared within the extension range.


±


±




±


±

z

µ
"j The fully-qualified name of the extension field. There must be a leading
 dot in front of the full name.



µ



µ





µ



µ
 !
¡

º
�
 The fully-qualified type name of the extension field. Unlike
 Metadata.type, Declaration.type must have a leading dot for messages
 and enums.


º


º




º


º

Î

¿
½
 If true, indicates that the number is reserved in the extension range,
 and any extension field with the number will fail to compile. Set this
 when a declared extension field is deleted.


¿


¿




¿


¿

Š

Ã
z If true, indicates that the extension must be defined as repeated.
 Otherwise the extension must be defined as optional.


Ã


Ã




Ã


Ã

$
	Å
" removed is_repeated


	Å



	
Å



	Å


±


Ë
F¢
 For external users: DO NOT USE. We are in the process of open sourcing
 extension declaration and executing internal cleanups before it can be
 used externally.



Ë




Ë




Ë
"


Ë
%&


Ë
'E


Ë
(D
=
Î
$/ Any features defined in the specific edition.


Î



Î



Î


Î
!#
@
Ñ
Õ
0 The verification state of the extension range.



Ñ

C
Ó
3 All the extensions of the range must be declared.



Ó


Ó



Ô




Ô



Ô

Ž

Ú
Û
;~ The verification state of the range.
 TODO: flip the default to DECLARATION once all empty ranges
 are marked as UNVERIFIED.


Ú



Ú



Ú
)

Ú
,-

Û
:

Û


Û
9
Z
Þ
M Clients can define custom options in extensions of this message. See above.



Þ





Þ




Þ

3
â
Ê
% Describes a field within a message.



â


ã
ƒ


ã

S
æ
C 0 is reserved for errors.
 Order is weird for historical reasons.



æ


æ



ç




ç



ç

w
ê
g Not ZigZag encoded.  Negative numbers take 10 bytes.  Use TYPE_SINT64 if
 negative values are likely.



ê


ê


ë



ë


ë

w
î
g Not ZigZag encoded.  Negative numbers take 10 bytes.  Use TYPE_SINT32 if
 negative values are likely.



î


î


ï



ï


ï


ð



ð


ð


ñ



ñ


ñ


ò



ò


ò

Æ
	ø
µ Tag-delimited aggregate.
 Group type is deprecated and not supported after google.protobuf. However, Proto3
 implementations should still be able to parse the group wire format and
 treat group fields as unknown fields.  In Editions, the group wire format
 can be enabled via the `message_encoding` feature.


	
ø


	ø

-

ù
" Length-delimited aggregate.




ù



ù

#
ü
 New in version 2.



ü


ü


ý



ý


ý



þ




þ



þ


ÿ



ÿ


ÿ


€


€

€
'
�" Uses ZigZag encoding.



�

�
'
‚" Uses ZigZag encoding.



‚

‚


…�



…
*

‡ 0 is reserved for errors




‡


‡



ˆ




ˆ



ˆ
Ì


Œ»
 The required label is only allowed in google.protobuf.  In proto3 and Editions
 it's explicitly prohibited.  In Editions, the `field_presence` feature
 can be used to get this behavior.




Œ


Œ

�

�


�


�

�


�


�



�



�


�

‘

‘


‘


‘

‘
œ

•�
 If type_name is set, this need not be set.  If both this and type_name
 are set, this must be one of TYPE_ENUM, TYPE_MESSAGE or TYPE_GROUP.


•


•


•

•
·
œ ¨ For message and enum types, this is the name of the type.  If the name
 starts with a '.', it is fully-qualified.  Otherwise, C++-like scoping
 rules are used to find the type (i.e. first the nested types within this
 message are searched, then within the parent, on up to the root
 namespace).


œ


œ


œ

œ
~
 p For extensions, this is the name of the type being extended.  It is
 resolved in the same manner as type_name.


 


 


 

 
‘
¦$‚ For numeric types, contains the original text representation of the value.
 For booleans, "true" or "false".
 For strings, contains the default text contents (not escaped in any way).
 For bytes, contains the C escaped value.  All bytes >= 128 are escaped.


¦


¦


¦

¦"#
„

ª!v If set, gives the index of a oneof in the containing type's oneof_decl
 list.  This field is a member of that oneof.


ª


ª


ª

ª 
ú

°!ë
 JSON name of this field. The value is set by protocol compiler. If the
 user has set a "json_name" option on this field, that option's value
 will be used. Otherwise, it's deduced from the field's name by converting
 it to camelCase.


°


°


°

° 

	²$

	²


	²

	
²

	²"#
°	

É%¡	 If true, this is a proto3 "optional". When a proto3 field is optional, it
 tracks presence regardless of field type.

 When proto3_optional is true, this field must belong to a oneof to signal
 to old proto3 clients that presence is tracked for this field. This oneof
 is known as a "synthetic" oneof, and this field must be its sole member
 (each proto3 optional field gets its own synthetic oneof). Synthetic oneofs
 exist in the descriptor only, and do not generate any API. Synthetic oneofs
 must be ordered after all "real" oneofs.

 For message fields, proto3_optional doesn't create any semantic change,
 since non-repeated message fields always track presence. However it still
 indicates the semantic detail of whether the user wrote "optional" or not.
 This can be useful for round-tripping the .proto file. For consistency we
 give message fields a synthetic oneof also, even though it is not required
 to track presence. This is especially important because the parser can't
 tell if a field is a message or an enum, so it must always create a
 synthetic oneof.

 Proto2 optional fields do not set this flag, because they already indicate
 optional with `LABEL_OPTIONAL`.



É



É



É


É"$
"
ÍÐ
 Describes a oneof.



Í

Î

Î


Î


Î

Î


Ï$


Ï



Ï



Ï


Ï"#
'
Óð
 Describes an enum type.



Ó

Ô

Ô


Ô


Ô

Ô


Ö.


Ö



Ö#



Ö$)


Ö,-

Ø#

Ø


Ø


Ø

Ø!"
¯
àãž Range of reserved numeric values. Reserved values may not be used by
 entries in the same enum. Reserved ranges may not overlap.

 Note that this is distinct from DescriptorProto.ReservedRange in that it
 is inclusive such that it can appropriately represent the entire int32
 domain.



à


á" Inclusive.


á

á



á

á


â" Inclusive.



â


â




â


â
ª

è0›
 Range of reserved numeric values. Reserved numeric values may not be used
 by enum values in the same enum declaration. Reserved ranges may not
 overlap.


è


è


è+

è./
l
ì$^ Reserved enum value names, which may not be reused. A given name may only
 be reserved once.


ì


ì


ì

ì"#
C
ï+5 Support for `export` and `local` keywords on enums.


ï


ï


ï&

ï)*
1
óø
# Describes a value within an enum.



ó 

ô

ô


ô


ô

ô


õ


õ



õ



õ


õ

÷(

÷


÷


÷#

÷&'
$
ûƒ
 Describes a service.



û

ü

ü


ü


ü

ü


ý,


ý



ý 



ý!'


ý*+

ÿ&

ÿ


ÿ


ÿ!

ÿ$%

	�

	�

	
�

	�


‚


‚
0
	†”
" Describes a method of a service.


	
†

	‡

	‡


	‡

	
‡

	‡
—

	
‹!ˆ
 Input and output type names.  These are resolved in the same way as
 FieldDescriptorProto.type_name, but must refer to a message type.


	
‹


	
‹

	

‹

	
‹ 

	Œ"

	Œ


	Œ

	
Œ

	Π!

	Ž%

	Ž


	Ž

	
Ž 

	Ž#$
E
	‘77 Identifies if client streams multiple client messages


	‘


	‘

	
‘ 

	‘#$

	‘%6

	‘05
E
	“77 Identifies if server streams multiple server messages


	“


	“

	
“ 

	“#$

	“%6

	“05
¯

¶Ç
2N ===================================================================
 Options
2Ð
 Each of the definitions above may have "options" attached.  These are
 just annotations which may cause code to be generated slightly differently
 or may contain hints for code that manipulates protocol messages.

 Clients may define custom options as extensions of the *Options messages.
 These extensions may not yet be known at parsing time, so the parser cannot
 store the values in them.  Instead it stores them in a field in the *Options
 message called uninterpreted_option. This field must have the same name
 across all *Options messages. We then use this field to populate the
 extensions when we build a descriptor, at which point all protos have been
 parsed and so all extensions are known.

 Extension numbers for custom options may be chosen as follows:
 * For options which will only be used within a single application or
   organization, or for experimental options, use field numbers 50000
   through 99999.  It is up to you to ensure that you do not use the
   same number for multiple options.
 * For options which will be published and used publicly by multiple
   independent entities, e-mail protobuf-global-extension-registry@google.com
   to reserve extension numbers. Simply provide your project name (e.g.
   Objective-C plugin) and your project website (if available) -- there's no
   need to explain how you intend to use them. Usually you only need one
   extension number. You can declare multiple options with only one extension
   number by putting them in a sub-message. See the Custom Options section of
   the docs for examples:
   https://developers.google.com/protocol-buffers/docs/proto#options
   If this turns out to be popular, a web service will be set up
   to automatically assign option numbers.




¶
ô


¼#å
 Sets the Java package where classes generated from this .proto will be
 placed.  By default, the proto package is used, but this is often
 inappropriate because proto packages do not normally start with backwards
 domain names.



¼



¼



¼


¼!"
ñ


Ã+â Controls the name of the wrapper Java class generated for the .proto file.
 That class will always contain the .proto file's getDescriptor() method as
 well as any top-level extensions defined in the .proto file.
 If java_multiple_files is disabled, then all the other classes from the
 .proto file will be nested inside the single wrapper outer class.




Ã




Ã




Ã&



Ã)*
¨

ËÕ— If enabled, then the Java code generator will generate a separate .java
 file for each top-level message, enum, and service defined in the .proto
 file.  Thus, these types will *not* be nested inside the wrapper class
 named by java_outer_classname.  However, the wrapper class will still be
 generated to contain the file's getDescriptor() method as well as any
 top-level extensions defined in the file.



Ë



Ë



Ë#


Ë&(


Ë)Õ


Ì


ÍÔ
)

ØE This option does nothing.



Ø



Ø



Ø-


Ø02


Ø3D


Ø4C
Ï

ä>À A proto2 file can set this to true to opt in to UTF-8 checking for Java,
 which will throw an exception if invalid UTF-8 is parsed from the wire or
 assigned to a string field.

 TODO: clarify exactly what kinds of field types this option
 applies to, and update these docs accordingly.

 Proto3 files already perform these checks. Setting the option explicitly to
 false has no effect: it cannot be used to opt proto3 files out of UTF-8
 checks.



ä



ä



ä&


ä)+


ä,=


ä7<
L

çì< Generated classes can be optimized for speed or code size.




ç
D

è"4 Generate complete code for parsing, serialization,




è	


è
G


ê etc.
"/ Use ReflectionOps to implement these methods.





ê



ê
G

ë"7 Generate code using MessageLite and the lite runtime.




ë


ë


í;


í



í



í$


í'(


í):


í49
â

ô"Ó Sets the Go package where structs generated from this .proto will be
 placed. If omitted, the Go package will be derived from the following:
   - The basename of the package import path, if provided.
   - Otherwise, the package statement in the .proto file, if present.
   - Otherwise, the basename of the .proto file, without extension.



ô



ô



ô


ô!
Ô

€;Å Should generic services be generated in each language?  "Generic" services
 are not specific to any particular RPC system.  They are generated by the
 main code generators in each language (without additional plugins).
 Generic services were the only kind of service generation supported by
 early versions of google.protobuf.

 Generic services are now considered deprecated in favor of using plugins
 that generate code specific to your particular RPC system.  Therefore,
 these default to false.  Old code which depends on generic services should
 explicitly set them to true.



€



€



€#


€&(


€):


€49


�=


�



�



�%


�(*


�+<


�6;


	‚;


	‚



	‚


	
‚#


	‚&(


	‚):


	‚49
+

	ƒ" removed php_generic_services



	ƒ


	
ƒ


	ƒ



„"



„!
ó



Š2ä
 Is this file deprecated?
 Depending on the target platform, this can emit Deprecated annotations
 for everything in the file, or it will be completely ignored; in the very
 least, this is a formalization for deprecating files.




Š




Š




Š



Š



Š 1



Š+0


Ž7q Enables the use of arenas for the proto messages in this file. This applies
 only to generated classes for C++.



Ž



Ž



Ž 


Ž#%


Ž&6


Ž15
’


’)ƒ
 Sets the objective c class prefix which is prepended to all objective c
 generated classes from this .proto. There is no default.



’



’



’#


’&(
I


•(; Namespace for generated classes; defaults to the package.




•




•




•"



•%'
‘

›$‚ By default Swift generators will take the proto package and CamelCase it
 replacing '.' with underscore and use that to prefix the types/symbols
 defined. When this options is provided, they will use this value instead
 to prefix the types/symbols defined.



›



›



›


›!#
~

Ÿ(p Sets the php class prefix which is prepended to all php generated classes
 from this .proto. Default is empty.



Ÿ



Ÿ



Ÿ"


Ÿ%'
¾


¤%¯
 Use this option to change the namespace of php generated classes. Default
 is empty. When this option is empty, the package name will be used for
 determining the namespace.



¤



¤



¤


¤"$
Ê


©.»
 Use this option to change the namespace of php generated metadata classes.
 Default is empty. When this option is empty, the proto file name will be
 used for determining the namespace.



©



©



©(


©+-
Â


®$³
 Use this option to change the package of ruby generated classes. Default
 is empty. When this option is not set, the package name will be used for
 determining the ruby package.



®



®



®


®!#
‘

´$‚ Any features defined in the specific edition.
 WARNING: This field should only be used by protobuf plugins or special
 cases like the proto compiler. Other uses are discouraged and
 developers should rely on the protoreflect APIs for their client language.



´



´



´


´!#
”


¸¼„
 Range reserved for first-class custom options defined by the Protobuf
 team. User custom options must use the 1000+ range instead.



¸




¸



¸


¸¼


¸¼
|

À:n The parser stores options it doesn't recognize here.
 See the documentation for the "Options" section above.



À



À



À3


À69
‡


Äz Clients can define custom options in extensions of this message.
 See the documentation for the "Options" section above.




Ä





Ä




Ä


	Æ


	
Æ


	

Æ


	
Æ

É 



É
Ø
Ü>É Set true to use the old proto1 MessageSet wire format for extensions.
 This is provided for backwards-compatibility with the MessageSet wire
 format.  You should not use this for any other reason:  It's less
 efficient, has fewer features, and is more complicated.

 The message must be defined exactly as follows:
   message Foo {
     option message_set_wire_format = true;
     extensions 4 to max;
   }
 Note that the message cannot have any defined fields; MessageSets only
 have extensions.

 All extensions of your type must be singular messages; e.g. they cannot
 be int32s, enums, or repeated messages.

 Because this is an option, the above two restrictions are not enforced by
 the protocol compiler.


Ü


Ü


Ü'

Ü*+

Ü,=

Ü7<
ë


áFÜ
 Disables the generation of the standard "descriptor()" accessor, which can
 conflict with a field of the same name.  This is meant to make migration
 from proto1 easier; new code should avoid fields named "descriptor".



á



á



á/


á23


á4E


á?D
î

ç1ß
 Is this message deprecated?
 Depending on the target platform, this can emit Deprecated annotations
 for the message, or it will be completely ignored; in the very least,
 this is a formalization for deprecating messages.


ç


ç


ç

ç

ç0

ç*/

	é

	é

	
é

	é

	
é

	

é

	
é

	é

	
é

	é
 
€‘ Whether the message is an automatically generated map entry type for the
 maps field.

 For maps fields:
     map<KeyType, ValueType> map_field = 1;
 The parsed descriptor looks like:
     message MapFieldEntry {
         option map_entry = true;
         optional KeyType key = 1;
         optional ValueType value = 2;
     }
     repeated MapFieldEntry map_field = 1;

 Implementations may choose not to generate the map_entry=true message, but
 use a native map in the target language to hold the keys and values.
 The reflection APIs in such implementations still need to work as
 if the field is a repeated message field.

 NOTE: Do not set the option in .proto files. Always use the maps syntax
 instead. The option should only be implicitly set by the proto compiler
 parser.


€


€


€

€
$
	‚
" javalite_serializable


	‚

	
‚

	‚

	ƒ
" javanano_as_lite


	ƒ

	
ƒ

	ƒ
Ý
�PÎ Enable the legacy handling of JSON field name conflicts.  This lowercases
 and strips underscored from the fields before comparison in proto3 only.
 The new behavior takes `json_name` into account and applies to proto2 as
 well.

 This should only be used as a temporary measure against broken builds due
 to the change in behavior for JSON field name conflicts.

 TODO This is legacy behavior we plan to remove once downstream
 teams have had time to migrate.


�


�


�6

�9;

�<O

�=N
‘
•$‚ Any features defined in the specific edition.
 WARNING: This field should only be used by protobuf plugins or special
 cases like the proto compiler. Other uses are discouraged and
 developers should rely on the protoreflect APIs for their client language.


•


•


•

•!#
’

™„
 Range reserved for first-class custom options defined by the Protobuf
 team. User custom options must use the 1000+ range instead.


™



™


™
O
œ:A The parser stores options it doesn't recognize here. See above.


œ


œ


œ3

œ69
Z
ŸM Clients can define custom options in extensions of this message. See above.



Ÿ




Ÿ



Ÿ

¢Ñ



¢
Â
ªE³ NOTE: ctype is deprecated. Use `features.(pb.cpp).string_type` instead.
 The ctype option instructs the C++ code generator to use a different
 representation of the field than it normally would.  See the specific
 options below.  This option is only implemented to support use of
 [ctype=CORD] and [ctype=STRING] (the default) on non-repeated fields of
 type "bytes" in the open source release.
 TODO: make ctype actually deprecated.


ª


ª


ª

ª

ªD

ª=C

«¸


«

­ Default mode.



­


­

–

µ
… The option [ctype=CORD] may be applied to a non-repeated field of type
 "bytes". It indicates that in C++, the data should be stored in a Cord
 instead of a string.  For very large strings, this may reduce memory
 fragmentation. It may also allow better performance when parsing from a
 Cord, or when parsing with aliasing enabled, as the parsed Cord may then
 alias the original buffer.




µ


µ

·


·

·
Ó

ÀÄ The packed option can be enabled for repeated primitive fields to enable
 a more efficient representation on the wire. Rather than repeatedly
 writing the tag and type for each element, the entire array is encoded as
 a single length-delimited blob. In proto3, only explicit setting it to
 false will avoid using packed encoding.  This option is prohibited in
 Editions, but the `repeated_field_encoding` feature can be used to control
 the behavior.



À



À



À


À
š
Í3‹ The jstype option determines the JavaScript type used for values of the
 field.  The option is permitted only for 64 bit integral and fixed types
 (int64, uint64, sint64, fixed64, sfixed64).  A field with jstype JS_STRING
 is represented as JavaScript string, which avoids loss of precision that
 can happen when a large value is converted to a floating point JavaScript.
 Specifying JS_NUMBER for the jstype causes the generated JavaScript code to
 use the JavaScript "number" type.  The behavior of the default option
 JS_NORMAL is implementation dependent.

 This option is an enum to permit additional types to be added, e.g.
 goog.math.Integer.


Í


Í


Í

Í

Í2

Í(1


Î×



Î
'

Ð Use the default type.




Ð


Ð
)


Ó Use JavaScript strings.





Ó



Ó
)

Ö Use JavaScript numbers.




Ö


Ö
™

ï+Š
 Should this field be parsed lazily?  Lazy applies only to message-type
 fields.  It means that when the outer message is initially parsed, the
 inner message's contents will not be parsed but instead stored in encoded
 form.  The inner message will actually be parsed when it is first accessed.

 This is only a hint.  Implementations are free to choose whether to use
 eager or lazy parsing regardless of the value of this option.  However,
 setting this option true suggests that the protocol author believes that
 using lazy parsing on this field is worth the additional bookkeeping
 overhead typically needed to implement it.

 This option does not affect the public interface of any generated code;
 all method signatures remain the same.  Furthermore, thread-safety of the
 interface is not affected by this option; const methods remain safe to
 call from multiple threads concurrently, while non-const methods continue
 to require exclusive access.

 Note that lazy message fields are still eagerly verified to check
 ill-formed wireformat or missing required fields. Calling IsInitialized()
 on the outer message would fail if the inner message has missing required
 fields. Failed verification would result in parsing failure (except when
 uninitialized messages are acceptable).


ï


ï


ï

ï

ï*

ï$)
¯

ô7 
 unverified_lazy does no correctness checks on the byte stream. This should
 only be used where lazy with verification is prohibitive for performance
 reasons.


ô


ô


ô

ô"$

ô%6

ô05
è

ú1Ù
 Is this field deprecated?
 Depending on the target platform, this can emit Deprecated annotations
 for accessors, or it will be completely ignored; in the very least, this
 is a formalization for deprecating fields.


ú


ú


ú

ú

ú0

ú*/
X
þ?J DEPRECATED. DO NOT USE!
 For Google-internal migration only. Do not use.


þ


þ


þ

þ

þ>

þ%*

þ,=
—

‚4ˆ
 Indicate that the field value should not be printed out when using debug
 formats, e.g. when the field contains sensitive credentials.


‚


‚


‚

‚!

‚"3

‚-2
Y
…‰I If set to RETENTION_SOURCE, the option will be omitted from the binary.



…

†


†

†


‡



‡


‡

ˆ


ˆ

ˆ

‹*

‹


‹


‹$

‹')
Ã

�›²
 This indicates the types of entities that the field may apply to when used
 as an option. If it is unset, then the field may be freely used as an
 option on any kind of entity.



�

‘


‘

‘


’



’


’

“$


“

“"#

”


”

”

•


•

•

–


–

–

—


—

—

˜


˜

˜

™


™

™

	š

	
š

	š

	�)

	�


	�

	
�#

	�&(

٢


Ÿ


 !

 

 



 

  
"

¡" Textproto value.



¡


¡




¡


¡


£0


£



£



£*


£-/
‘
©$‚ Any features defined in the specific edition.
 WARNING: This field should only be used by protobuf plugins or special
 cases like the proto compiler. Other uses are discouraged and
 developers should rely on the protoreflect APIs for their client language.


©


©


©

©!#
D

¬Â4 Information about the support window of a feature.




¬

Ô


°,Ã
 The edition that this feature was first available in.  In editions
 earlier than this one, the default assigned to EDITION_LEGACY will be
 used, and proto files will not be able to override it.



°


°




°'


°*+
w


´,g The edition this feature becomes deprecated in.  Using this after this
 edition may trigger warnings.




´



´





´'



´*+
v

¸,f The deprecation warning text if this feature is used after the edition it
 was marked deprecated in.



¸


¸




¸'


¸*+
¾


½)­
 The edition this feature is no longer available in.  In editions after
 this one, the last default assigned will be used, and proto files will
 not be able to override it.



½


½




½$


½'(
f

Á&V The removal error text if this feature is used after the edition it was
 removed in.



Á


Á




Á!


Á$%

Ã/

Ã


Ã


Ã)

Ã,.
’

Ç„
 Range reserved for first-class custom options defined by the Protobuf
 team. User custom options must use the 1000+ range instead.


Ç



Ç


Ç
O

Ê:A The parser stores options it doesn't recognize here. See above.



Ê



Ê



Ê3


Ê69
Z
ÍM Clients can define custom options in extensions of this message. See above.



Í




Í



Í

	Ï
" removed jtype


	Ï

	
Ï

	Ï
9
	Ð", reserve target, target_obsolete_do_not_use


	
Ð

	

Ð

	
Ð


Óã




Ó
‘

Ø#‚ Any features defined in the specific edition.
 WARNING: This field should only be used by protobuf plugins or special
 cases like the proto compiler. Other uses are discouraged and
 developers should rely on the protoreflect APIs for their client language.



Ø



Ø



Ø


Ø!"
’


Ü„
 Range reserved for first-class custom options defined by the Protobuf
 team. User custom options must use the 1000+ range instead.



Ü




Ü



Ü
O


ß:A The parser stores options it doesn't recognize here. See above.




ß




ß




ß3



ß69
Z

âM Clients can define custom options in extensions of this message. See above.




â





â




â

åŠ



å
`
é R Set this option to true to allow mapping different tag names to the same
 value.


é


é


é

é
å


ï1Ö
 Is this enum deprecated?
 Depending on the target platform, this can emit Deprecated annotations
 for the enum, or it will be completely ignored; in the very least, this
 is a formalization for deprecating enums.



ï



ï



ï


ï


ï0


ï*/

	ñ
" javanano_as_lite


	ñ

	
ñ

	ñ
È
ùO¹ Enable the legacy handling of JSON field name conflicts.  This lowercases
 and strips underscored from the fields before comparison in proto3 only.
 The new behavior takes `json_name` into account and applies to proto2 as
 well.
 TODO Remove this legacy behavior once downstream teams have
 had time to migrate.


ù


ù


ù6

ù9:

ù;N

ù<M
‘
ÿ#‚ Any features defined in the specific edition.
 WARNING: This field should only be used by protobuf plugins or special
 cases like the proto compiler. Other uses are discouraged and
 developers should rely on the protoreflect APIs for their client language.


ÿ


ÿ


ÿ

ÿ!"
’

ƒ„
 Range reserved for first-class custom options defined by the Protobuf
 team. User custom options must use the 1000+ range instead.


ƒ



ƒ


ƒ
O
†:A The parser stores options it doesn't recognize here. See above.


†


†


†3

†69
Z
‰M Clients can define custom options in extensions of this message. See above.



‰




‰



‰

Ψ



Œ
÷

‘1è
 Is this enum value deprecated?
 Depending on the target platform, this can emit Deprecated annotations
 for the enum value, or it will be completely ignored; in the very least,
 this is a formalization for deprecating enum values.


‘


‘


‘

‘

‘0

‘*/
‘

—#‚ Any features defined in the specific edition.
 WARNING: This field should only be used by protobuf plugins or special
 cases like the proto compiler. Other uses are discouraged and
 developers should rely on the protoreflect APIs for their client language.



—



—



—


—!"
®

œ3Ÿ
 Indicate that fields annotated with this enum value should not be printed
 out when using debug formats, e.g. when the field contains sensitive
 credentials.


œ


œ


œ

œ 

œ!2

œ,1
H
Ÿ;: Information about the support window of a feature value.


Ÿ


Ÿ&


Ÿ'6

Ÿ9:
’

£§‚
 Range reserved for first-class extension options defined by the Protobuf
 team. Custom options must use the 1000+ range instead.


£



£


£

£§

£§
O
ª:A The parser stores options it doesn't recognize here. See above.


ª


ª


ª3

ª69
Z
­M Clients can define custom options in extensions of this message. See above.



­




­



­

°Ì



°
‘
¶$‚ Any features defined in the specific edition.
 WARNING: This field should only be used by protobuf plugins or special
 cases like the proto compiler. Other uses are discouraged and
 developers should rely on the protoreflect APIs for their client language.


¶


¶


¶

¶!#
Ù

Á2ß
 Is this service deprecated?
 Depending on the target platform, this can emit Deprecated annotations
 for the service, or it will be completely ignored; in the very least,
 this is a formalization for deprecating services.
2è
 Note:  Field numbers 1 through 32 are reserved for Google's internal RPC
   framework.  We apologize for hoarding these numbers to ourselves, but
   we were already using them long before we decided to release Protocol
   Buffers.



Á



Á



Á


Á


Á 1


Á+0
’

Å„
 Range reserved for first-class custom options defined by the Protobuf
 team. User custom options must use the 1000+ range instead.


Å



Å


Å
O
È:A The parser stores options it doesn't recognize here. See above.


È


È


È3

È69
Z
ËM Clients can define custom options in extensions of this message. See above.



Ë




Ë



Ë

Îõ



Î
Ö
Ù2Ü
 Is this method deprecated?
 Depending on the target platform, this can emit Deprecated annotations
 for the method, or it will be completely ignored; in the very least,
 this is a formalization for deprecating methods.
2è
 Note:  Field numbers 1 through 32 are reserved for Google's internal RPC
   framework.  We apologize for hoarding these numbers to ourselves, but
   we were already using them long before we decided to release Protocol
   Buffers.


Ù


Ù


Ù

Ù

Ù 1

Ù+0
ð

Þâß
 Is this method side-effect-free (or safe in HTTP parlance), or idempotent,
 or neither? HTTP based RPC implementation may choose GET verb for safe
 methods, and PUT verb for idempotent methods instead of the default POST.



Þ

ß


ß

ß
$

à" implies idempotent




à


à
7
á"' idempotent, but may have side effects



á

á


ãä&


ã



ã



ã-


ã02


ä%


ä$
‘
ê$‚ Any features defined in the specific edition.
 WARNING: This field should only be used by protobuf plugins or special
 cases like the proto compiler. Other uses are discouraged and
 developers should rely on the protoreflect APIs for their client language.


ê


ê


ê

ê!#
’

î„
 Range reserved for first-class custom options defined by the Protobuf
 team. User custom options must use the 1000+ range instead.


î



î


î
O
ñ:A The parser stores options it doesn't recognize here. See above.


ñ


ñ


ñ3

ñ69
Z
ôM Clients can define custom options in extensions of this message. See above.



ô




ô



ô
‹
ý‘
ü A message representing a option the parser does not recognize. This only
 appears in options protos created by the compiler::Parser class.
 DescriptorPool resolves these when building Descriptor objects. Therefore,
 options protos in descriptor objects (e.g. returned by Descriptor::options(),
 or produced by Descriptor::CopyTo()) will never have UninterpretedOptions
 in them.



ý
Ë
ƒ†º The name of the uninterpreted option.  Each string represents a segment in
 a dot-separated name.  is_extension is true iff a segment represents an
 extension (denoted with parentheses in options specs in .proto files).
 E.g.,{ ["foo", false], ["bar.baz", true], ["moo", false] } represents
 "foo.(bar.baz).moo".



ƒ


„"

„

„



„

„ !


…#


…


…




…


…!"

‡

‡


‡


‡

‡
œ


‹'�
 The value of the uninterpreted option, in whatever type the tokenizer
 identified it as during parsing. Exactly one of these should be set.



‹



‹



‹"


‹%&

Œ)

Œ


Œ


Œ$

Œ'(

�(

�


�


�#

�&'

Ž#

Ž


Ž


Ž

Ž!"

�"

�


�


�

� !

�&

�


�


�!

�$%
Û
œ‚

û TODO Enums in C++ gencode (and potentially other languages) are
 not well scoped.  This means that each of the feature enums below can clash
 with each other.  The short names we've chosen maximize call-site
 readability, but leave us very open to this scenario.  A future feature will
 be designed and implemented to handle this, hopefully before we ever hit a
 conflict here.
2O ===================================================================
 Features



œ

�¢


�

ž


ž

ž


Ÿ



Ÿ


Ÿ

 


 

 

¡


¡

¡

£­

£


£


£'

£*+

£,­

¤!

¥


¦

§©

ªE


«E

¬C


¯³



¯


°



°


°



±




±



±


²



²



²



´½


´



´



´


´ !


´"½


µ!


¶



·


¸º


»C



¼A

¿Ã


¿

À(


À#

À&'


Á



Á



Á


Â


Â

Â

ÄÍ

Ä


Ä 


Ä!8

Ä;<

Ä=Í

Å!

Æ


Ç

ÈÊ

ËE


ÌC

ÏÔ


Ï

Ð 


Ð

Ð


Ñ



Ñ



Ñ


Ò


Ò

Ò

Ó

Ó



Ó


Ó


ÕÞ

Õ


Õ


Õ)

Õ,-

Õ.Þ

Ö!

×


Ø

ÙÛ

ÜA


ÝC

àä


à

á!


á

á 


â



â


â

ã


ã

ã

åí

å


å


å+

å./

å0í

æ!

ç


è

éë

ìL

ïó


ï

ð


ð

ð


ñ



ñ	


ñ

ò


ò

ò

ôþ

ô


ô


ô!

ô$%

ô&þ

õ!

ö!


÷

ø

ùû

üO


ýB

€	…	


€	

�	%


�	 

�	#$


‚	



‚	


‚	

ƒ	


ƒ	

ƒ	

„	


„	

„	

†	—	

†	


†	


†	2

†	56

†	7—	

‡	 

ˆ	


‰	)

Š	!

‹	

Œ	

�	

Ž	$

�	!

�	 

‘	“	

”	I


•	D

–	D

™	¬	


™	


š	ª	


š		 

›	,

	
›	'

	›	*+
N

ž	< Default pre-EDITION_2024, all UNSET visibility are export.


	

ž	

	
ž	
U
¡	C All top-level symbols default to export, nested default to local.


	
¡	

	¡	
1
¤	 All symbols default to local.


	
¤	

	¤	
É

©	¶
 All symbols local by default. Nested types cannot be exported.
 With special case caveat for message { enum {} reserved 1 to max; }
 This is the recommended setting for new protos.


	
©	

	©	

	«	

	«	


	
«	


	«	

­	¶	

­	


­	4


­	5N

®	

®	¶	

¯	$

°	"

±	³		

´	K


µ	O


¸	Æ	



¸	



¹	Å	



¹		


º	

	

º	

	
º	
�


À	$î
 Default pre-EDITION_2026: there are no limit enforcement at the protoc
 level. Practical limits still exist, but they will tend to fail while
 compiling protoc-generated code, and these limits tend to be language
 or toolchain specific.


	


À	

	

À	"#
Ÿ


Ä	Œ
 A set of limits enforced by Edition 2026 by default. For a detailed
 list of all the limits please consult the Edition 2026 documentation.


	

Ä	

	
Ä	

Ç	Õ	

Ç	


Ç	0


Ç	1E

Ç	HI

Ç	JÕ	

È	 

É	


Ê	!

Ë	

Ì	

Í	Ï	

Ð	Ó	


Ô	K

	×	

	×	

	
×	

	×	

Ù	þ	

Ù	



Ù	


Ù	

Ù	þ	

Ú	Þ	


ß	ã	

ä	O

å	é	

ê	î	

ï	ó	

ô	ø	

ù	ý	
#
€
" For internal testing



€





€




€

:
�
"- for https://github.com/bufbuild/protobuf-es


�




�



�


¬
ˆ
¢

� A compiled specification for the defaults of a set of features.  These
 messages are generated from FeatureSet extensions and can be used to seed
 feature resolution. The resolution with this object becomes a simple search
 for the closest matching edition, followed by proto merges.



ˆ

°
�
˜
Ÿ A map from every known edition with a unique set of defaults to its
 defaults. Not all editions may be contained here.  For a given edition,
 the defaults at the closest matching edition ordered at or before it should
 be used.  This field must be in strict ascending order by edition.



�

"

Ž
!

Ž


Ž




Ž


Ž
 
N

‘
1> Defaults of features that can be overridden in this edition.



‘



‘





‘
,


‘
/0
P
”
+@ Defaults of features that can't be overridden in this edition.


”


”




”
&

”
)*

	–


	–



	
–



	–



	
–


	

–


	
–



—



—



™
1

™



™
#


™
$,

™
/0
‚


�
't The minimum supported edition (inclusive) when this was constructed.
 Editions before this will not have defaults.



�




�




�
"


�
%&
†

¡
'x The maximum known edition (inclusive) when this was constructed. Editions
 after this will not have reliable defaults.


¡



¡



¡
"

¡
%&
Ú

©
±
j Encapsulates information about the original source file from which a
 FileDescriptorProto was generated.
2` ===================================================================
 Optional source code info



©

‚
Õ
!ó A Location identifies a piece of source code in a .proto file which
 corresponds to a particular definition.  This information is intended
 to be useful to IDEs, code indexers, documentation generators, and similar
 tools.

 For example, say we have a file like:
   message Foo {
     optional string foo = 1;
   }
 Let's look at just the field definition:
   optional string foo = 1;
   ^       ^^     ^^  ^  ^^^
   a       bc     de  f  ghi
 We have the following locations:
   span   path               represents
   [a,i)  [ 4, 0, 2, 0 ]     The whole field definition.
   [a,b)  [ 4, 0, 2, 0, 4 ]  The label (optional).
   [c,d)  [ 4, 0, 2, 0, 5 ]  The type (string).
   [e,f)  [ 4, 0, 2, 0, 1 ]  The name (foo).
   [g,h)  [ 4, 0, 2, 0, 3 ]  The number (1).

 Notes:
 - A location may refer to a repeated field itself (i.e. not to any
   particular index within it).  This is used whenever a set of elements are
   logically enclosed in a single code segment.  For example, an entire
   extend block (possibly containing multiple extension definitions) will
   have an outer location whose path refers to the "extensions" repeated
   field without an index.
 - Multiple locations may have the same path.  This happens when a single
   logical declaration is spread out across multiple places.  The most
   obvious example is the "extend" block again -- there may be multiple
   extend blocks in the same scope, each of which will have the same path.
 - A location's span is not always a subset of its parent's span.  For
   example, the "extendee" of an extension declaration appears at the
   beginning of the "extend" block and is shared by all extensions within
   the block.
 - Just because a location's span is a subset of some other location's span
   does not mean that it is a descendant.  For example, a "group" defines
   both a type and a field in a single declaration.  Thus, the locations
   corresponding to the type and field and their components will overlap.
 - Code which tries to interpret locations should probably be designed to
   ignore those that it doesn't understand, as more types of locations could
   be recorded in the future.


Õ