1// Protocol Buffers - Google's data interchange format
2// Copyright 2008 Google Inc.  All rights reserved.
3// https://developers.google.com/protocol-buffers/
4//
5// Redistribution and use in source and binary forms, with or without
6// modification, are permitted provided that the following conditions are
7// met:
8//
9//     * Redistributions of source code must retain the above copyright
10// notice, this list of conditions and the following disclaimer.
11//     * Redistributions in binary form must reproduce the above
12// copyright notice, this list of conditions and the following disclaimer
13// in the documentation and/or other materials provided with the
14// distribution.
15//     * Neither the name of Google Inc. nor the names of its
16// contributors may be used to endorse or promote products derived from
17// this software without specific prior written permission.
18//
19// THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
20// "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
21// LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
22// A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
23// OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
24// SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
25// LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
26// DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
27// THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
28// (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
29// OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
30
31// Author: kenton@google.com (Kenton Varda)
32//  Based on original Protocol Buffers design by
33//  Sanjay Ghemawat, Jeff Dean, and others.
34//
35// The messages in this file describe the definitions found in .proto files.
36// A valid .proto file can be translated directly to a FileDescriptorProto
37// without any other information (e.g. without reading its imports).
38
39
40syntax = "proto2";
41
42package google.protobuf;
43option go_package = "github.com/golang/protobuf/protoc-gen-go/descriptor;descriptor";
44option java_package = "com.google.protobuf";
45option java_outer_classname = "DescriptorProtos";
46option csharp_namespace = "Google.Protobuf.Reflection";
47option objc_class_prefix = "GPB";
48option cc_enable_arenas = true;
49
50// descriptor.proto must be optimized for speed because reflection-based
51// algorithms don't work during bootstrapping.
52option optimize_for = SPEED;
53
54// The protocol compiler can output a FileDescriptorSet containing the .proto
55// files it parses.
56message FileDescriptorSet {
57  repeated FileDescriptorProto file = 1;
58}
59
60// Describes a complete .proto file.
61message FileDescriptorProto {
62  optional string name = 1;       // file name, relative to root of source tree
63  optional string package = 2;    // e.g. "foo", "foo.bar", etc.
64
65  // Names of files imported by this file.
66  repeated string dependency = 3;
67  // Indexes of the public imported files in the dependency list above.
68  repeated int32 public_dependency = 10;
69  // Indexes of the weak imported files in the dependency list.
70  // For Google-internal migration only. Do not use.
71  repeated int32 weak_dependency = 11;
72
73  // All top-level definitions in this file.
74  repeated DescriptorProto message_type = 4;
75  repeated EnumDescriptorProto enum_type = 5;
76  repeated ServiceDescriptorProto service = 6;
77  repeated FieldDescriptorProto extension = 7;
78
79  optional FileOptions options = 8;
80
81  // This field contains optional information about the original source code.
82  // You may safely remove this entire field without harming runtime
83  // functionality of the descriptors -- the information is needed only by
84  // development tools.
85  optional SourceCodeInfo source_code_info = 9;
86
87  // The syntax of the proto file.
88  // The supported values are "proto2" and "proto3".
89  optional string syntax = 12;
90}
91
92// Describes a message type.
93message DescriptorProto {
94  optional string name = 1;
95
96  repeated FieldDescriptorProto field = 2;
97  repeated FieldDescriptorProto extension = 6;
98
99  repeated DescriptorProto nested_type = 3;
100  repeated EnumDescriptorProto enum_type = 4;
101
102  message ExtensionRange {
103    optional int32 start = 1;
104    optional int32 end = 2;
105
106    optional ExtensionRangeOptions options = 3;
107  }
108  repeated ExtensionRange extension_range = 5;
109
110  repeated OneofDescriptorProto oneof_decl = 8;
111
112  optional MessageOptions options = 7;
113
114  // Range of reserved tag numbers. Reserved tag numbers may not be used by
115  // fields or extension ranges in the same message. Reserved ranges may
116  // not overlap.
117  message ReservedRange {
118    optional int32 start = 1; // Inclusive.
119    optional int32 end = 2;   // Exclusive.
120  }
121  repeated ReservedRange reserved_range = 9;
122  // Reserved field names, which may not be used by fields in the same message.
123  // A given name may only be reserved once.
124  repeated string reserved_name = 10;
125}
126
127message ExtensionRangeOptions {
128  // The parser stores options it doesn't recognize here. See above.
129  repeated UninterpretedOption uninterpreted_option = 999;
130
131  // Clients can define custom options in extensions of this message. See above.
132  extensions 1000 to max;
133}
134
135// Describes a field within a message.
136message FieldDescriptorProto {
137  enum Type {
138    // 0 is reserved for errors.
139    // Order is weird for historical reasons.
140    TYPE_DOUBLE         = 1;
141    TYPE_FLOAT          = 2;
142    // Not ZigZag encoded.  Negative numbers take 10 bytes.  Use TYPE_SINT64 if
143    // negative values are likely.
144    TYPE_INT64          = 3;
145    TYPE_UINT64         = 4;
146    // Not ZigZag encoded.  Negative numbers take 10 bytes.  Use TYPE_SINT32 if
147    // negative values are likely.
148    TYPE_INT32          = 5;
149    TYPE_FIXED64        = 6;
150    TYPE_FIXED32        = 7;
151    TYPE_BOOL           = 8;
152    TYPE_STRING         = 9;
153    // Tag-delimited aggregate.
154    // Group type is deprecated and not supported in proto3. However, Proto3
155    // implementations should still be able to parse the group wire format and
156    // treat group fields as unknown fields.
157    TYPE_GROUP          = 10;
158    TYPE_MESSAGE        = 11;  // Length-delimited aggregate.
159
160    // New in version 2.
161    TYPE_BYTES          = 12;
162    TYPE_UINT32         = 13;
163    TYPE_ENUM           = 14;
164    TYPE_SFIXED32       = 15;
165    TYPE_SFIXED64       = 16;
166    TYPE_SINT32         = 17;  // Uses ZigZag encoding.
167    TYPE_SINT64         = 18;  // Uses ZigZag encoding.
168  };
169
170  enum Label {
171    // 0 is reserved for errors
172    LABEL_OPTIONAL      = 1;
173    LABEL_REQUIRED      = 2;
174    LABEL_REPEATED      = 3;
175  };
176
177  optional string name = 1;
178  optional int32 number = 3;
179  optional Label label = 4;
180
181  // If type_name is set, this need not be set.  If both this and type_name
182  // are set, this must be one of TYPE_ENUM, TYPE_MESSAGE or TYPE_GROUP.
183  optional Type type = 5;
184
185  // For message and enum types, this is the name of the type.  If the name
186  // starts with a '.', it is fully-qualified.  Otherwise, C++-like scoping
187  // rules are used to find the type (i.e. first the nested types within this
188  // message are searched, then within the parent, on up to the root
189  // namespace).
190  optional string type_name = 6;
191
192  // For extensions, this is the name of the type being extended.  It is
193  // resolved in the same manner as type_name.
194  optional string extendee = 2;
195
196  // For numeric types, contains the original text representation of the value.
197  // For booleans, "true" or "false".
198  // For strings, contains the default text contents (not escaped in any way).
199  // For bytes, contains the C escaped value.  All bytes >= 128 are escaped.
200  // TODO(kenton):  Base-64 encode?
201  optional string default_value = 7;
202
203  // If set, gives the index of a oneof in the containing type's oneof_decl
204  // list.  This field is a member of that oneof.
205  optional int32 oneof_index = 9;
206
207  // JSON name of this field. The value is set by protocol compiler. If the
208  // user has set a "json_name" option on this field, that option's value
209  // will be used. Otherwise, it's deduced from the field's name by converting
210  // it to camelCase.
211  optional string json_name = 10;
212
213  optional FieldOptions options = 8;
214}
215
216// Describes a oneof.
217message OneofDescriptorProto {
218  optional string name = 1;
219  optional OneofOptions options = 2;
220}
221
222// Describes an enum type.
223message EnumDescriptorProto {
224  optional string name = 1;
225
226  repeated EnumValueDescriptorProto value = 2;
227
228  optional EnumOptions options = 3;
229
230  // Range of reserved numeric values. Reserved values may not be used by
231  // entries in the same enum. Reserved ranges may not overlap.
232  //
233  // Note that this is distinct from DescriptorProto.ReservedRange in that it
234  // is inclusive such that it can appropriately represent the entire int32
235  // domain.
236  message EnumReservedRange {
237    optional int32 start = 1; // Inclusive.
238    optional int32 end = 2;   // Inclusive.
239  }
240
241  // Range of reserved numeric values. Reserved numeric values may not be used
242  // by enum values in the same enum declaration. Reserved ranges may not
243  // overlap.
244  repeated EnumReservedRange reserved_range = 4;
245
246  // Reserved enum value names, which may not be reused. A given name may only
247  // be reserved once.
248  repeated string reserved_name = 5;
249}
250
251// Describes a value within an enum.
252message EnumValueDescriptorProto {
253  optional string name = 1;
254  optional int32 number = 2;
255
256  optional EnumValueOptions options = 3;
257}
258
259// Describes a service.
260message ServiceDescriptorProto {
261  optional string name = 1;
262  repeated MethodDescriptorProto method = 2;
263
264  optional ServiceOptions options = 3;
265}
266
267// Describes a method of a service.
268message MethodDescriptorProto {
269  optional string name = 1;
270
271  // Input and output type names.  These are resolved in the same way as
272  // FieldDescriptorProto.type_name, but must refer to a message type.
273  optional string input_type = 2;
274  optional string output_type = 3;
275
276  optional MethodOptions options = 4;
277
278  // Identifies if client streams multiple client messages
279  optional bool client_streaming = 5 [default=false];
280  // Identifies if server streams multiple server messages
281  optional bool server_streaming = 6 [default=false];
282}
283
284
285// ===================================================================
286// Options
287
288// Each of the definitions above may have "options" attached.  These are
289// just annotations which may cause code to be generated slightly differently
290// or may contain hints for code that manipulates protocol messages.
291//
292// Clients may define custom options as extensions of the *Options messages.
293// These extensions may not yet be known at parsing time, so the parser cannot
294// store the values in them.  Instead it stores them in a field in the *Options
295// message called uninterpreted_option. This field must have the same name
296// across all *Options messages. We then use this field to populate the
297// extensions when we build a descriptor, at which point all protos have been
298// parsed and so all extensions are known.
299//
300// Extension numbers for custom options may be chosen as follows:
301// * For options which will only be used within a single application or
302//   organization, or for experimental options, use field numbers 50000
303//   through 99999.  It is up to you to ensure that you do not use the
304//   same number for multiple options.
305// * For options which will be published and used publicly by multiple
306//   independent entities, e-mail protobuf-global-extension-registry@google.com
307//   to reserve extension numbers. Simply provide your project name (e.g.
308//   Objective-C plugin) and your project website (if available) -- there's no
309//   need to explain how you intend to use them. Usually you only need one
310//   extension number. You can declare multiple options with only one extension
311//   number by putting them in a sub-message. See the Custom Options section of
312//   the docs for examples:
313//   https://developers.google.com/protocol-buffers/docs/proto#options
314//   If this turns out to be popular, a web service will be set up
315//   to automatically assign option numbers.
316
317
318message FileOptions {
319
320  // Sets the Java package where classes generated from this .proto will be
321  // placed.  By default, the proto package is used, but this is often
322  // inappropriate because proto packages do not normally start with backwards
323  // domain names.
324  optional string java_package = 1;
325
326
327  // If set, all the classes from the .proto file are wrapped in a single
328  // outer class with the given name.  This applies to both Proto1
329  // (equivalent to the old "--one_java_file" option) and Proto2 (where
330  // a .proto always translates to a single class, but you may want to
331  // explicitly choose the class name).
332  optional string java_outer_classname = 8;
333
334  // If set true, then the Java code generator will generate a separate .java
335  // file for each top-level message, enum, and service defined in the .proto
336  // file.  Thus, these types will *not* be nested inside the outer class
337  // named by java_outer_classname.  However, the outer class will still be
338  // generated to contain the file's getDescriptor() method as well as any
339  // top-level extensions defined in the file.
340  optional bool java_multiple_files = 10 [default=false];
341
342  // This option does nothing.
343  optional bool java_generate_equals_and_hash = 20 [deprecated=true];
344
345  // If set true, then the Java2 code generator will generate code that
346  // throws an exception whenever an attempt is made to assign a non-UTF-8
347  // byte sequence to a string field.
348  // Message reflection will do the same.
349  // However, an extension field still accepts non-UTF-8 byte sequences.
350  // This option has no effect on when used with the lite runtime.
351  optional bool java_string_check_utf8 = 27 [default=false];
352
353
354  // Generated classes can be optimized for speed or code size.
355  enum OptimizeMode {
356    SPEED = 1;        // Generate complete code for parsing, serialization,
357                      // etc.
358    CODE_SIZE = 2;    // Use ReflectionOps to implement these methods.
359    LITE_RUNTIME = 3; // Generate code using MessageLite and the lite runtime.
360  }
361  optional OptimizeMode optimize_for = 9 [default=SPEED];
362
363  // Sets the Go package where structs generated from this .proto will be
364  // placed. If omitted, the Go package will be derived from the following:
365  //   - The basename of the package import path, if provided.
366  //   - Otherwise, the package statement in the .proto file, if present.
367  //   - Otherwise, the basename of the .proto file, without extension.
368  optional string go_package = 11;
369
370
371
372  // Should generic services be generated in each language?  "Generic" services
373  // are not specific to any particular RPC system.  They are generated by the
374  // main code generators in each language (without additional plugins).
375  // Generic services were the only kind of service generation supported by
376  // early versions of google.protobuf.
377  //
378  // Generic services are now considered deprecated in favor of using plugins
379  // that generate code specific to your particular RPC system.  Therefore,
380  // these default to false.  Old code which depends on generic services should
381  // explicitly set them to true.
382  optional bool cc_generic_services = 16 [default=false];
383  optional bool java_generic_services = 17 [default=false];
384  optional bool py_generic_services = 18 [default=false];
385  optional bool php_generic_services = 42 [default=false];
386
387  // Is this file deprecated?
388  // Depending on the target platform, this can emit Deprecated annotations
389  // for everything in the file, or it will be completely ignored; in the very
390  // least, this is a formalization for deprecating files.
391  optional bool deprecated = 23 [default=false];
392
393  // Enables the use of arenas for the proto messages in this file. This applies
394  // only to generated classes for C++.
395  optional bool cc_enable_arenas = 31 [default=false];
396
397
398  // Sets the objective c class prefix which is prepended to all objective c
399  // generated classes from this .proto. There is no default.
400  optional string objc_class_prefix = 36;
401
402  // Namespace for generated classes; defaults to the package.
403  optional string csharp_namespace = 37;
404
405  // By default Swift generators will take the proto package and CamelCase it
406  // replacing '.' with underscore and use that to prefix the types/symbols
407  // defined. When this options is provided, they will use this value instead
408  // to prefix the types/symbols defined.
409  optional string swift_prefix = 39;
410
411  // Sets the php class prefix which is prepended to all php generated classes
412  // from this .proto. Default is empty.
413  optional string php_class_prefix = 40;
414
415  // Use this option to change the namespace of php generated classes. Default
416  // is empty. When this option is empty, the package name will be used for
417  // determining the namespace.
418  optional string php_namespace = 41;
419
420  // The parser stores options it doesn't recognize here.
421  // See the documentation for the "Options" section above.
422  repeated UninterpretedOption uninterpreted_option = 999;
423
424  // Clients can define custom options in extensions of this message.
425  // See the documentation for the "Options" section above.
426  extensions 1000 to max;
427
428  reserved 38;
429}
430
431message MessageOptions {
432  // Set true to use the old proto1 MessageSet wire format for extensions.
433  // This is provided for backwards-compatibility with the MessageSet wire
434  // format.  You should not use this for any other reason:  It's less
435  // efficient, has fewer features, and is more complicated.
436  //
437  // The message must be defined exactly as follows:
438  //   message Foo {
439  //     option message_set_wire_format = true;
440  //     extensions 4 to max;
441  //   }
442  // Note that the message cannot have any defined fields; MessageSets only
443  // have extensions.
444  //
445  // All extensions of your type must be singular messages; e.g. they cannot
446  // be int32s, enums, or repeated messages.
447  //
448  // Because this is an option, the above two restrictions are not enforced by
449  // the protocol compiler.
450  optional bool message_set_wire_format = 1 [default=false];
451
452  // Disables the generation of the standard "descriptor()" accessor, which can
453  // conflict with a field of the same name.  This is meant to make migration
454  // from proto1 easier; new code should avoid fields named "descriptor".
455  optional bool no_standard_descriptor_accessor = 2 [default=false];
456
457  // Is this message deprecated?
458  // Depending on the target platform, this can emit Deprecated annotations
459  // for the message, or it will be completely ignored; in the very least,
460  // this is a formalization for deprecating messages.
461  optional bool deprecated = 3 [default=false];
462
463  // Whether the message is an automatically generated map entry type for the
464  // maps field.
465  //
466  // For maps fields:
467  //     map<KeyType, ValueType> map_field = 1;
468  // The parsed descriptor looks like:
469  //     message MapFieldEntry {
470  //         option map_entry = true;
471  //         optional KeyType key = 1;
472  //         optional ValueType value = 2;
473  //     }
474  //     repeated MapFieldEntry map_field = 1;
475  //
476  // Implementations may choose not to generate the map_entry=true message, but
477  // use a native map in the target language to hold the keys and values.
478  // The reflection APIs in such implementions still need to work as
479  // if the field is a repeated message field.
480  //
481  // NOTE: Do not set the option in .proto files. Always use the maps syntax
482  // instead. The option should only be implicitly set by the proto compiler
483  // parser.
484  optional bool map_entry = 7;
485
486  reserved 8;  // javalite_serializable
487  reserved 9;  // javanano_as_lite
488
489  // The parser stores options it doesn't recognize here. See above.
490  repeated UninterpretedOption uninterpreted_option = 999;
491
492  // Clients can define custom options in extensions of this message. See above.
493  extensions 1000 to max;
494}
495
496message FieldOptions {
497  // The ctype option instructs the C++ code generator to use a different
498  // representation of the field than it normally would.  See the specific
499  // options below.  This option is not yet implemented in the open source
500  // release -- sorry, we'll try to include it in a future version!
501  optional CType ctype = 1 [default = STRING];
502  enum CType {
503    // Default mode.
504    STRING = 0;
505
506    CORD = 1;
507
508    STRING_PIECE = 2;
509  }
510  // The packed option can be enabled for repeated primitive fields to enable
511  // a more efficient representation on the wire. Rather than repeatedly
512  // writing the tag and type for each element, the entire array is encoded as
513  // a single length-delimited blob. In proto3, only explicit setting it to
514  // false will avoid using packed encoding.
515  optional bool packed = 2;
516
517  // The jstype option determines the JavaScript type used for values of the
518  // field.  The option is permitted only for 64 bit integral and fixed types
519  // (int64, uint64, sint64, fixed64, sfixed64).  A field with jstype JS_STRING
520  // is represented as JavaScript string, which avoids loss of precision that
521  // can happen when a large value is converted to a floating point JavaScript.
522  // Specifying JS_NUMBER for the jstype causes the generated JavaScript code to
523  // use the JavaScript "number" type.  The behavior of the default option
524  // JS_NORMAL is implementation dependent.
525  //
526  // This option is an enum to permit additional types to be added, e.g.
527  // goog.math.Integer.
528  optional JSType jstype = 6 [default = JS_NORMAL];
529  enum JSType {
530    // Use the default type.
531    JS_NORMAL = 0;
532
533    // Use JavaScript strings.
534    JS_STRING = 1;
535
536    // Use JavaScript numbers.
537    JS_NUMBER = 2;
538  }
539
540  // Should this field be parsed lazily?  Lazy applies only to message-type
541  // fields.  It means that when the outer message is initially parsed, the
542  // inner message's contents will not be parsed but instead stored in encoded
543  // form.  The inner message will actually be parsed when it is first accessed.
544  //
545  // This is only a hint.  Implementations are free to choose whether to use
546  // eager or lazy parsing regardless of the value of this option.  However,
547  // setting this option true suggests that the protocol author believes that
548  // using lazy parsing on this field is worth the additional bookkeeping
549  // overhead typically needed to implement it.
550  //
551  // This option does not affect the public interface of any generated code;
552  // all method signatures remain the same.  Furthermore, thread-safety of the
553  // interface is not affected by this option; const methods remain safe to
554  // call from multiple threads concurrently, while non-const methods continue
555  // to require exclusive access.
556  //
557  //
558  // Note that implementations may choose not to check required fields within
559  // a lazy sub-message.  That is, calling IsInitialized() on the outer message
560  // may return true even if the inner message has missing required fields.
561  // This is necessary because otherwise the inner message would have to be
562  // parsed in order to perform the check, defeating the purpose of lazy
563  // parsing.  An implementation which chooses not to check required fields
564  // must be consistent about it.  That is, for any particular sub-message, the
565  // implementation must either *always* check its required fields, or *never*
566  // check its required fields, regardless of whether or not the message has
567  // been parsed.
568  optional bool lazy = 5 [default=false];
569
570  // Is this field deprecated?
571  // Depending on the target platform, this can emit Deprecated annotations
572  // for accessors, or it will be completely ignored; in the very least, this
573  // is a formalization for deprecating fields.
574  optional bool deprecated = 3 [default=false];
575
576  // For Google-internal migration only. Do not use.
577  optional bool weak = 10 [default=false];
578
579
580  // The parser stores options it doesn't recognize here. See above.
581  repeated UninterpretedOption uninterpreted_option = 999;
582
583  // Clients can define custom options in extensions of this message. See above.
584  extensions 1000 to max;
585
586  reserved 4;  // removed jtype
587}
588
589message OneofOptions {
590  // The parser stores options it doesn't recognize here. See above.
591  repeated UninterpretedOption uninterpreted_option = 999;
592
593  // Clients can define custom options in extensions of this message. See above.
594  extensions 1000 to max;
595}
596
597message EnumOptions {
598
599  // Set this option to true to allow mapping different tag names to the same
600  // value.
601  optional bool allow_alias = 2;
602
603  // Is this enum deprecated?
604  // Depending on the target platform, this can emit Deprecated annotations
605  // for the enum, or it will be completely ignored; in the very least, this
606  // is a formalization for deprecating enums.
607  optional bool deprecated = 3 [default=false];
608
609  reserved 5;  // javanano_as_lite
610
611  // The parser stores options it doesn't recognize here. See above.
612  repeated UninterpretedOption uninterpreted_option = 999;
613
614  // Clients can define custom options in extensions of this message. See above.
615  extensions 1000 to max;
616}
617
618message EnumValueOptions {
619  // Is this enum value deprecated?
620  // Depending on the target platform, this can emit Deprecated annotations
621  // for the enum value, or it will be completely ignored; in the very least,
622  // this is a formalization for deprecating enum values.
623  optional bool deprecated = 1 [default=false];
624
625  // The parser stores options it doesn't recognize here. See above.
626  repeated UninterpretedOption uninterpreted_option = 999;
627
628  // Clients can define custom options in extensions of this message. See above.
629  extensions 1000 to max;
630}
631
632message ServiceOptions {
633
634  // Note:  Field numbers 1 through 32 are reserved for Google's internal RPC
635  //   framework.  We apologize for hoarding these numbers to ourselves, but
636  //   we were already using them long before we decided to release Protocol
637  //   Buffers.
638
639  // Is this service deprecated?
640  // Depending on the target platform, this can emit Deprecated annotations
641  // for the service, or it will be completely ignored; in the very least,
642  // this is a formalization for deprecating services.
643  optional bool deprecated = 33 [default=false];
644
645  // The parser stores options it doesn't recognize here. See above.
646  repeated UninterpretedOption uninterpreted_option = 999;
647
648  // Clients can define custom options in extensions of this message. See above.
649  extensions 1000 to max;
650}
651
652message MethodOptions {
653
654  // Note:  Field numbers 1 through 32 are reserved for Google's internal RPC
655  //   framework.  We apologize for hoarding these numbers to ourselves, but
656  //   we were already using them long before we decided to release Protocol
657  //   Buffers.
658
659  // Is this method deprecated?
660  // Depending on the target platform, this can emit Deprecated annotations
661  // for the method, or it will be completely ignored; in the very least,
662  // this is a formalization for deprecating methods.
663  optional bool deprecated = 33 [default=false];
664
665  // Is this method side-effect-free (or safe in HTTP parlance), or idempotent,
666  // or neither? HTTP based RPC implementation may choose GET verb for safe
667  // methods, and PUT verb for idempotent methods instead of the default POST.
668  enum IdempotencyLevel {
669    IDEMPOTENCY_UNKNOWN = 0;
670    NO_SIDE_EFFECTS     = 1; // implies idempotent
671    IDEMPOTENT          = 2; // idempotent, but may have side effects
672  }
673  optional IdempotencyLevel idempotency_level =
674      34 [default=IDEMPOTENCY_UNKNOWN];
675
676  // The parser stores options it doesn't recognize here. See above.
677  repeated UninterpretedOption uninterpreted_option = 999;
678
679  // Clients can define custom options in extensions of this message. See above.
680  extensions 1000 to max;
681}
682
683
684// A message representing a option the parser does not recognize. This only
685// appears in options protos created by the compiler::Parser class.
686// DescriptorPool resolves these when building Descriptor objects. Therefore,
687// options protos in descriptor objects (e.g. returned by Descriptor::options(),
688// or produced by Descriptor::CopyTo()) will never have UninterpretedOptions
689// in them.
690message UninterpretedOption {
691  // The name of the uninterpreted option.  Each string represents a segment in
692  // a dot-separated name.  is_extension is true iff a segment represents an
693  // extension (denoted with parentheses in options specs in .proto files).
694  // E.g.,{ ["foo", false], ["bar.baz", true], ["qux", false] } represents
695  // "foo.(bar.baz).qux".
696  message NamePart {
697    required string name_part = 1;
698    required bool is_extension = 2;
699  }
700  repeated NamePart name = 2;
701
702  // The value of the uninterpreted option, in whatever type the tokenizer
703  // identified it as during parsing. Exactly one of these should be set.
704  optional string identifier_value = 3;
705  optional uint64 positive_int_value = 4;
706  optional int64 negative_int_value = 5;
707  optional double double_value = 6;
708  optional bytes string_value = 7;
709  optional string aggregate_value = 8;
710}
711
712// ===================================================================
713// Optional source code info
714
715// Encapsulates information about the original source file from which a
716// FileDescriptorProto was generated.
717message SourceCodeInfo {
718  // A Location identifies a piece of source code in a .proto file which
719  // corresponds to a particular definition.  This information is intended
720  // to be useful to IDEs, code indexers, documentation generators, and similar
721  // tools.
722  //
723  // For example, say we have a file like:
724  //   message Foo {
725  //     optional string foo = 1;
726  //   }
727  // Let's look at just the field definition:
728  //   optional string foo = 1;
729  //   ^       ^^     ^^  ^  ^^^
730  //   a       bc     de  f  ghi
731  // We have the following locations:
732  //   span   path               represents
733  //   [a,i)  [ 4, 0, 2, 0 ]     The whole field definition.
734  //   [a,b)  [ 4, 0, 2, 0, 4 ]  The label (optional).
735  //   [c,d)  [ 4, 0, 2, 0, 5 ]  The type (string).
736  //   [e,f)  [ 4, 0, 2, 0, 1 ]  The name (foo).
737  //   [g,h)  [ 4, 0, 2, 0, 3 ]  The number (1).
738  //
739  // Notes:
740  // - A location may refer to a repeated field itself (i.e. not to any
741  //   particular index within it).  This is used whenever a set of elements are
742  //   logically enclosed in a single code segment.  For example, an entire
743  //   extend block (possibly containing multiple extension definitions) will
744  //   have an outer location whose path refers to the "extensions" repeated
745  //   field without an index.
746  // - Multiple locations may have the same path.  This happens when a single
747  //   logical declaration is spread out across multiple places.  The most
748  //   obvious example is the "extend" block again -- there may be multiple
749  //   extend blocks in the same scope, each of which will have the same path.
750  // - A location's span is not always a subset of its parent's span.  For
751  //   example, the "extendee" of an extension declaration appears at the
752  //   beginning of the "extend" block and is shared by all extensions within
753  //   the block.
754  // - Just because a location's span is a subset of some other location's span
755  //   does not mean that it is a descendent.  For example, a "group" defines
756  //   both a type and a field in a single declaration.  Thus, the locations
757  //   corresponding to the type and field and their components will overlap.
758  // - Code which tries to interpret locations should probably be designed to
759  //   ignore those that it doesn't understand, as more types of locations could
760  //   be recorded in the future.
761  repeated Location location = 1;
762  message Location {
763    // Identifies which part of the FileDescriptorProto was defined at this
764    // location.
765    //
766    // Each element is a field number or an index.  They form a path from
767    // the root FileDescriptorProto to the place where the definition.  For
768    // example, this path:
769    //   [ 4, 3, 2, 7, 1 ]
770    // refers to:
771    //   file.message_type(3)  // 4, 3
772    //       .field(7)         // 2, 7
773    //       .name()           // 1
774    // This is because FileDescriptorProto.message_type has field number 4:
775    //   repeated DescriptorProto message_type = 4;
776    // and DescriptorProto.field has field number 2:
777    //   repeated FieldDescriptorProto field = 2;
778    // and FieldDescriptorProto.name has field number 1:
779    //   optional string name = 1;
780    //
781    // Thus, the above path gives the location of a field name.  If we removed
782    // the last element:
783    //   [ 4, 3, 2, 7 ]
784    // this path refers to the whole field declaration (from the beginning
785    // of the label to the terminating semicolon).
786    repeated int32 path = 1 [packed=true];
787
788    // Always has exactly three or four elements: start line, start column,
789    // end line (optional, otherwise assumed same as start line), end column.
790    // These are packed into a single field for efficiency.  Note that line
791    // and column numbers are zero-based -- typically you will want to add
792    // 1 to each before displaying to a user.
793    repeated int32 span = 2 [packed=true];
794
795    // If this SourceCodeInfo represents a complete declaration, these are any
796    // comments appearing before and after the declaration which appear to be
797    // attached to the declaration.
798    //
799    // A series of line comments appearing on consecutive lines, with no other
800    // tokens appearing on those lines, will be treated as a single comment.
801    //
802    // leading_detached_comments will keep paragraphs of comments that appear
803    // before (but not connected to) the current element. Each paragraph,
804    // separated by empty lines, will be one comment element in the repeated
805    // field.
806    //
807    // Only the comment content is provided; comment markers (e.g. //) are
808    // stripped out.  For block comments, leading whitespace and an asterisk
809    // will be stripped from the beginning of each line other than the first.
810    // Newlines are included in the output.
811    //
812    // Examples:
813    //
814    //   optional int32 foo = 1;  // Comment attached to foo.
815    //   // Comment attached to bar.
816    //   optional int32 bar = 2;
817    //
818    //   optional string baz = 3;
819    //   // Comment attached to baz.
820    //   // Another line attached to baz.
821    //
822    //   // Comment attached to qux.
823    //   //
824    //   // Another line attached to qux.
825    //   optional double qux = 4;
826    //
827    //   // Detached comment for corge. This is not leading or trailing comments
828    //   // to qux or corge because there are blank lines separating it from
829    //   // both.
830    //
831    //   // Detached comment for corge paragraph 2.
832    //
833    //   optional string corge = 5;
834    //   /* Block comment attached
835    //    * to corge.  Leading asterisks
836    //    * will be removed. */
837    //   /* Block comment attached to
838    //    * grault. */
839    //   optional int32 grault = 6;
840    //
841    //   // ignored detached comments.
842    optional string leading_comments = 3;
843    optional string trailing_comments = 4;
844    repeated string leading_detached_comments = 6;
845  }
846}
847
848// Describes the relationship between generated code and its original source
849// file. A GeneratedCodeInfo message is associated with only one generated
850// source file, but may contain references to different source .proto files.
851message GeneratedCodeInfo {
852  // An Annotation connects some span of text in generated code to an element
853  // of its generating .proto file.
854  repeated Annotation annotation = 1;
855  message Annotation {
856    // Identifies the element in the original source .proto file. This field
857    // is formatted the same as SourceCodeInfo.Location.path.
858    repeated int32 path = 1 [packed=true];
859
860    // Identifies the filesystem path to the original source .proto.
861    optional string source_file = 2;
862
863    // Identifies the starting offset in bytes in the generated code
864    // that relates to the identified object.
865    optional int32 begin = 3;
866
867    // Identifies the ending offset in bytes in the generated code that
868    // relates to the identified offset. The end offset should be one past
869    // the last relevant byte (so the length of the text = end - begin).
870    optional int32 end = 4;
871  }
872}
873