Package com.google.protobuf.compiler

Interface PluginProtos.CodeGeneratorRequestOrBuilder

All Superinterfaces:
com.google.protobuf.MessageLiteOrBuilder, com.google.protobuf.MessageOrBuilder
All Known Implementing Classes:
PluginProtos.CodeGeneratorRequest, PluginProtos.CodeGeneratorRequest.Builder
Enclosing class:
PluginProtos
public static interface PluginProtos.CodeGeneratorRequestOrBuilder extends com.google.protobuf.MessageOrBuilder

  • Method Details

    • getFileToGenerateList

      List<String> getFileToGenerateList()
       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.
      repeated string file_to_generate = 1;
      Returns:
      A list containing the fileToGenerate.

    • getFileToGenerateCount

      int getFileToGenerateCount()
       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.
      repeated string file_to_generate = 1;
      Returns:
      The count of fileToGenerate.

    • getFileToGenerate

      String getFileToGenerate(int index)
       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.
      repeated string file_to_generate = 1;
      Parameters:
      index - The index of the element to return.
      Returns:
      The fileToGenerate at the given index.

    • getFileToGenerateBytes

      com.google.protobuf.ByteString getFileToGenerateBytes(int index)
       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.
      repeated string file_to_generate = 1;
      Parameters:
      index - The index of the value to return.
      Returns:
      The bytes of the fileToGenerate at the given index.

    • hasParameter

      boolean hasParameter()
       The generator parameter passed on the command-line.
      optional string parameter = 2;
      Returns:
      Whether the parameter field is set.

    • getParameter

      String getParameter()
       The generator parameter passed on the command-line.
      optional string parameter = 2;
      Returns:
      The parameter.

    • getParameterBytes

      com.google.protobuf.ByteString getParameterBytes()
       The generator parameter passed on the command-line.
      optional string parameter = 2;
      Returns:
      The bytes for parameter.

    • getProtoFileList

      List<DescriptorProtos.FileDescriptorProto> getProtoFileList()
       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.
 Type names of fields and extensions in the FileDescriptorProto are always
 fully qualified.
      repeated .google.protobuf.FileDescriptorProto proto_file = 15;

    • getProtoFile

      DescriptorProtos.FileDescriptorProto getProtoFile(int index)
       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.
 Type names of fields and extensions in the FileDescriptorProto are always
 fully qualified.
      repeated .google.protobuf.FileDescriptorProto proto_file = 15;

    • getProtoFileCount

      int getProtoFileCount()
       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.
 Type names of fields and extensions in the FileDescriptorProto are always
 fully qualified.
      repeated .google.protobuf.FileDescriptorProto proto_file = 15;

    • getProtoFileOrBuilderList

      List<? extends DescriptorProtos.FileDescriptorProtoOrBuilder> getProtoFileOrBuilderList()
       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.
 Type names of fields and extensions in the FileDescriptorProto are always
 fully qualified.
      repeated .google.protobuf.FileDescriptorProto proto_file = 15;

    • getProtoFileOrBuilder

      DescriptorProtos.FileDescriptorProtoOrBuilder getProtoFileOrBuilder(int index)
       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.
 Type names of fields and extensions in the FileDescriptorProto are always
 fully qualified.
      repeated .google.protobuf.FileDescriptorProto proto_file = 15;

    • hasCompilerVersion

      boolean hasCompilerVersion()
       The version number of protocol compiler.
      optional .google.protobuf.compiler.Version compiler_version = 3;
      Returns:
      Whether the compilerVersion field is set.

    • getCompilerVersion

      PluginProtos.Version getCompilerVersion()
       The version number of protocol compiler.
      optional .google.protobuf.compiler.Version compiler_version = 3;
      Returns:
      The compilerVersion.

    • getCompilerVersionOrBuilder

      PluginProtos.VersionOrBuilder getCompilerVersionOrBuilder()
       The version number of protocol compiler.
      optional .google.protobuf.compiler.Version compiler_version = 3;