public static interface PluginProtos.CodeGeneratorRequestOrBuilder extends MessageOrBuilder
Modifier and Type | Method and Description |
---|---|
String |
getFileToGenerate(int index)
repeated string file_to_generate = 1; |
ByteString |
getFileToGenerateBytes(int index)
repeated string file_to_generate = 1; |
int |
getFileToGenerateCount()
repeated string file_to_generate = 1; |
ProtocolStringList |
getFileToGenerateList()
repeated string file_to_generate = 1; |
String |
getParameter()
optional string parameter = 2; |
ByteString |
getParameterBytes()
optional string parameter = 2; |
DescriptorProtos.FileDescriptorProto |
getProtoFile(int index)
repeated .google.protobuf.FileDescriptorProto proto_file = 15; |
int |
getProtoFileCount()
repeated .google.protobuf.FileDescriptorProto proto_file = 15; |
List<DescriptorProtos.FileDescriptorProto> |
getProtoFileList()
repeated .google.protobuf.FileDescriptorProto proto_file = 15; |
DescriptorProtos.FileDescriptorProtoOrBuilder |
getProtoFileOrBuilder(int index)
repeated .google.protobuf.FileDescriptorProto proto_file = 15; |
List<? extends DescriptorProtos.FileDescriptorProtoOrBuilder> |
getProtoFileOrBuilderList()
repeated .google.protobuf.FileDescriptorProto proto_file = 15; |
boolean |
hasParameter()
optional string parameter = 2; |
findInitializationErrors, getAllFields, getDefaultInstanceForType, getDescriptorForType, getField, getInitializationErrorString, getOneofFieldDescriptor, getRepeatedField, getRepeatedFieldCount, getUnknownFields, hasField, hasOneof
isInitialized
ProtocolStringList getFileToGenerateList()
repeated string file_to_generate = 1;
The .proto files that were explicitly listed on the command-line. The code generator should generate code only for these files. Each file's descriptor will be included in proto_file, below.
int getFileToGenerateCount()
repeated string file_to_generate = 1;
The .proto files that were explicitly listed on the command-line. The code generator should generate code only for these files. Each file's descriptor will be included in proto_file, below.
String getFileToGenerate(int index)
repeated string file_to_generate = 1;
The .proto files that were explicitly listed on the command-line. The code generator should generate code only for these files. Each file's descriptor will be included in proto_file, below.
ByteString getFileToGenerateBytes(int index)
repeated string file_to_generate = 1;
The .proto files that were explicitly listed on the command-line. The code generator should generate code only for these files. Each file's descriptor will be included in proto_file, below.
boolean hasParameter()
optional string parameter = 2;
The generator parameter passed on the command-line.
String getParameter()
optional string parameter = 2;
The generator parameter passed on the command-line.
ByteString getParameterBytes()
optional string parameter = 2;
The generator parameter passed on the command-line.
List<DescriptorProtos.FileDescriptorProto> getProtoFileList()
repeated .google.protobuf.FileDescriptorProto proto_file = 15;
FileDescriptorProtos for all files in files_to_generate and everything they import. The files will appear in topological order, so each file appears before any file that imports it. protoc guarantees that all proto_files will be written after the fields above, even though this is not technically guaranteed by the protobuf wire format. This theoretically could allow a plugin to stream in the FileDescriptorProtos and handle them one by one rather than read the entire set into memory at once. However, as of this writing, this is not similarly optimized on protoc's end -- it will store all fields in memory at once before sending them to the plugin.
DescriptorProtos.FileDescriptorProto getProtoFile(int index)
repeated .google.protobuf.FileDescriptorProto proto_file = 15;
FileDescriptorProtos for all files in files_to_generate and everything they import. The files will appear in topological order, so each file appears before any file that imports it. protoc guarantees that all proto_files will be written after the fields above, even though this is not technically guaranteed by the protobuf wire format. This theoretically could allow a plugin to stream in the FileDescriptorProtos and handle them one by one rather than read the entire set into memory at once. However, as of this writing, this is not similarly optimized on protoc's end -- it will store all fields in memory at once before sending them to the plugin.
int getProtoFileCount()
repeated .google.protobuf.FileDescriptorProto proto_file = 15;
FileDescriptorProtos for all files in files_to_generate and everything they import. The files will appear in topological order, so each file appears before any file that imports it. protoc guarantees that all proto_files will be written after the fields above, even though this is not technically guaranteed by the protobuf wire format. This theoretically could allow a plugin to stream in the FileDescriptorProtos and handle them one by one rather than read the entire set into memory at once. However, as of this writing, this is not similarly optimized on protoc's end -- it will store all fields in memory at once before sending them to the plugin.
List<? extends DescriptorProtos.FileDescriptorProtoOrBuilder> getProtoFileOrBuilderList()
repeated .google.protobuf.FileDescriptorProto proto_file = 15;
FileDescriptorProtos for all files in files_to_generate and everything they import. The files will appear in topological order, so each file appears before any file that imports it. protoc guarantees that all proto_files will be written after the fields above, even though this is not technically guaranteed by the protobuf wire format. This theoretically could allow a plugin to stream in the FileDescriptorProtos and handle them one by one rather than read the entire set into memory at once. However, as of this writing, this is not similarly optimized on protoc's end -- it will store all fields in memory at once before sending them to the plugin.
DescriptorProtos.FileDescriptorProtoOrBuilder getProtoFileOrBuilder(int index)
repeated .google.protobuf.FileDescriptorProto proto_file = 15;
FileDescriptorProtos for all files in files_to_generate and everything they import. The files will appear in topological order, so each file appears before any file that imports it. protoc guarantees that all proto_files will be written after the fields above, even though this is not technically guaranteed by the protobuf wire format. This theoretically could allow a plugin to stream in the FileDescriptorProtos and handle them one by one rather than read the entire set into memory at once. However, as of this writing, this is not similarly optimized on protoc's end -- it will store all fields in memory at once before sending them to the plugin.
Copyright © 2008–2016 Google. All rights reserved.