Class PluginProtos.CodeGeneratorResponse.File.Builder

All Implemented Interfaces:
PluginProtos.CodeGeneratorResponse.FileOrBuilder, Message.Builder, MessageLite.Builder, MessageLiteOrBuilder, MessageOrBuilder, Cloneable
Enclosing class:
PluginProtos.CodeGeneratorResponse.File

public static final class PluginProtos.CodeGeneratorResponse.File.Builder extends GeneratedMessageV3.Builder<PluginProtos.CodeGeneratorResponse.File.Builder> implements PluginProtos.CodeGeneratorResponse.FileOrBuilder
 Represents a single generated file.
 
Protobuf type google.protobuf.compiler.CodeGeneratorResponse.File
  • Field Details

  • Constructor Details

  • Method Details

    • getDescriptor

      public static final Descriptors.Descriptor getDescriptor()
    • internalGetFieldAccessorTable

      protected GeneratedMessageV3.FieldAccessorTable internalGetFieldAccessorTable()
      Description copied from class: GeneratedMessageV3.Builder
      Get the FieldAccessorTable for this type. We can't have the message class pass this in to the constructor because of bootstrapping trouble with DescriptorProtos.
      Specified by:
      internalGetFieldAccessorTable in class GeneratedMessageV3.Builder<PluginProtos.CodeGeneratorResponse.File.Builder>
    • maybeForceBuilderInitialization

      private void maybeForceBuilderInitialization()
    • clear

      Description copied from class: GeneratedMessageV3.Builder
      Called by the initialization and clear code paths to allow subclasses to reset any of their builtin fields back to the initial values.
      Specified by:
      clear in interface Message.Builder
      Specified by:
      clear in interface MessageLite.Builder
      Overrides:
      clear in class GeneratedMessageV3.Builder<PluginProtos.CodeGeneratorResponse.File.Builder>
    • getDescriptorForType

      public Descriptors.Descriptor getDescriptorForType()
      Description copied from interface: Message.Builder
      Get the message's type's descriptor. See MessageOrBuilder.getDescriptorForType().
      Specified by:
      getDescriptorForType in interface Message.Builder
      Specified by:
      getDescriptorForType in interface MessageOrBuilder
      Overrides:
      getDescriptorForType in class GeneratedMessageV3.Builder<PluginProtos.CodeGeneratorResponse.File.Builder>
    • getDefaultInstanceForType

      public PluginProtos.CodeGeneratorResponse.File getDefaultInstanceForType()
      Description copied from interface: MessageLiteOrBuilder
      Get an instance of the type with no fields set. Because no fields are set, all getters for singular fields will return default values and repeated fields will appear empty. This may or may not be a singleton. This differs from the getDefaultInstance() method of generated message classes in that this method is an abstract method of the MessageLite interface whereas getDefaultInstance() is a static method of a specific class. They return the same thing.
      Specified by:
      getDefaultInstanceForType in interface MessageLiteOrBuilder
      Specified by:
      getDefaultInstanceForType in interface MessageOrBuilder
    • build

      Description copied from interface: MessageLite.Builder
      Constructs the message based on the state of the Builder. Subsequent changes to the Builder will not affect the returned message.
      Specified by:
      build in interface Message.Builder
      Specified by:
      build in interface MessageLite.Builder
    • buildPartial

      Description copied from interface: MessageLite.Builder
      Like MessageLite.Builder.build(), but does not throw an exception if the message is missing required fields. Instead, a partial message is returned. Subsequent changes to the Builder will not affect the returned message.
      Specified by:
      buildPartial in interface Message.Builder
      Specified by:
      buildPartial in interface MessageLite.Builder
    • clone

      Description copied from interface: MessageLite.Builder
      Clones the Builder.
      Specified by:
      clone in interface Message.Builder
      Specified by:
      clone in interface MessageLite.Builder
      Overrides:
      clone in class GeneratedMessageV3.Builder<PluginProtos.CodeGeneratorResponse.File.Builder>
      See Also:
    • setField

      Description copied from interface: Message.Builder
      Sets a field to the given value. The value must be of the correct type for this field, i.e. the same type that MessageOrBuilder.getField(Descriptors.FieldDescriptor) would return.
      Specified by:
      setField in interface Message.Builder
      Overrides:
      setField in class GeneratedMessageV3.Builder<PluginProtos.CodeGeneratorResponse.File.Builder>
    • clearField

      Description copied from interface: Message.Builder
      Clears the field. This is exactly equivalent to calling the generated "clear" accessor method corresponding to the field.
      Specified by:
      clearField in interface Message.Builder
      Overrides:
      clearField in class GeneratedMessageV3.Builder<PluginProtos.CodeGeneratorResponse.File.Builder>
    • clearOneof

      Description copied from class: AbstractMessage.Builder
      TODO(jieluo): Clear it when all subclasses have implemented this method.
      Specified by:
      clearOneof in interface Message.Builder
      Overrides:
      clearOneof in class GeneratedMessageV3.Builder<PluginProtos.CodeGeneratorResponse.File.Builder>
    • setRepeatedField

      public PluginProtos.CodeGeneratorResponse.File.Builder setRepeatedField(Descriptors.FieldDescriptor field, int index, Object value)
      Description copied from interface: Message.Builder
      Sets an element of a repeated field to the given value. The value must be of the correct type for this field, i.e. the same type that MessageOrBuilder.getRepeatedField(Descriptors.FieldDescriptor,int) would return.
      Specified by:
      setRepeatedField in interface Message.Builder
      Overrides:
      setRepeatedField in class GeneratedMessageV3.Builder<PluginProtos.CodeGeneratorResponse.File.Builder>
    • addRepeatedField

      Description copied from interface: Message.Builder
      Like setRepeatedField, but appends the value as a new element.
      Specified by:
      addRepeatedField in interface Message.Builder
      Overrides:
      addRepeatedField in class GeneratedMessageV3.Builder<PluginProtos.CodeGeneratorResponse.File.Builder>
    • mergeFrom

      Description copied from interface: Message.Builder
      Merge other into the message being built. other must have the exact same type as this (i.e. getDescriptorForType() == other.getDescriptorForType()).

      Merging occurs as follows. For each field:
      * For singular primitive fields, if the field is set in other, then other's value overwrites the value in this message.
      * For singular message fields, if the field is set in other, it is merged into the corresponding sub-message of this message using the same merging rules.
      * For repeated fields, the elements in other are concatenated with the elements in this message.
      * For oneof groups, if the other message has one of the fields set, the group of this message is cleared and replaced by the field of the other message, so that the oneof constraint is preserved.

      This is equivalent to the Message::MergeFrom method in C++.

      Specified by:
      mergeFrom in interface Message.Builder
      Overrides:
      mergeFrom in class AbstractMessage.Builder<PluginProtos.CodeGeneratorResponse.File.Builder>
    • mergeFrom

    • isInitialized

      public final boolean isInitialized()
      Description copied from interface: MessageLiteOrBuilder
      Returns true if all required fields in the message and all embedded messages are set, false otherwise.

      See also: MessageOrBuilder.getInitializationErrorString()

      Specified by:
      isInitialized in interface MessageLiteOrBuilder
      Overrides:
      isInitialized in class GeneratedMessageV3.Builder<PluginProtos.CodeGeneratorResponse.File.Builder>
    • mergeFrom

      Description copied from interface: MessageLite.Builder
      Like MessageLite.Builder.mergeFrom(CodedInputStream), but also parses extensions. The extensions that you want to be able to parse must be registered in extensionRegistry. Extensions not in the registry will be treated as unknown fields.
      Specified by:
      mergeFrom in interface Message.Builder
      Specified by:
      mergeFrom in interface MessageLite.Builder
      Overrides:
      mergeFrom in class AbstractMessage.Builder<PluginProtos.CodeGeneratorResponse.File.Builder>
      Throws:
      IOException
    • hasName

      public boolean hasName()
       The file name, relative to the output directory.  The name must not
       contain "." or ".." components and must be relative, not be absolute (so,
       the file cannot lie outside the output directory).  "/" must be used as
       the path separator, not "\".
       If the name is omitted, the content will be appended to the previous
       file.  This allows the generator to break large files into small chunks,
       and allows the generated text to be streamed back to protoc so that large
       files need not reside completely in memory at one time.  Note that as of
       this writing protoc does not optimize for this -- it will read the entire
       CodeGeneratorResponse before writing files to disk.
       
      optional string name = 1;
      Specified by:
      hasName in interface PluginProtos.CodeGeneratorResponse.FileOrBuilder
      Returns:
      Whether the name field is set.
    • getName

      public String getName()
       The file name, relative to the output directory.  The name must not
       contain "." or ".." components and must be relative, not be absolute (so,
       the file cannot lie outside the output directory).  "/" must be used as
       the path separator, not "\".
       If the name is omitted, the content will be appended to the previous
       file.  This allows the generator to break large files into small chunks,
       and allows the generated text to be streamed back to protoc so that large
       files need not reside completely in memory at one time.  Note that as of
       this writing protoc does not optimize for this -- it will read the entire
       CodeGeneratorResponse before writing files to disk.
       
      optional string name = 1;
      Specified by:
      getName in interface PluginProtos.CodeGeneratorResponse.FileOrBuilder
      Returns:
      The name.
    • getNameBytes

      public ByteString getNameBytes()
       The file name, relative to the output directory.  The name must not
       contain "." or ".." components and must be relative, not be absolute (so,
       the file cannot lie outside the output directory).  "/" must be used as
       the path separator, not "\".
       If the name is omitted, the content will be appended to the previous
       file.  This allows the generator to break large files into small chunks,
       and allows the generated text to be streamed back to protoc so that large
       files need not reside completely in memory at one time.  Note that as of
       this writing protoc does not optimize for this -- it will read the entire
       CodeGeneratorResponse before writing files to disk.
       
      optional string name = 1;
      Specified by:
      getNameBytes in interface PluginProtos.CodeGeneratorResponse.FileOrBuilder
      Returns:
      The bytes for name.
    • setName

       The file name, relative to the output directory.  The name must not
       contain "." or ".." components and must be relative, not be absolute (so,
       the file cannot lie outside the output directory).  "/" must be used as
       the path separator, not "\".
       If the name is omitted, the content will be appended to the previous
       file.  This allows the generator to break large files into small chunks,
       and allows the generated text to be streamed back to protoc so that large
       files need not reside completely in memory at one time.  Note that as of
       this writing protoc does not optimize for this -- it will read the entire
       CodeGeneratorResponse before writing files to disk.
       
      optional string name = 1;
      Parameters:
      value - The name to set.
      Returns:
      This builder for chaining.
    • clearName

       The file name, relative to the output directory.  The name must not
       contain "." or ".." components and must be relative, not be absolute (so,
       the file cannot lie outside the output directory).  "/" must be used as
       the path separator, not "\".
       If the name is omitted, the content will be appended to the previous
       file.  This allows the generator to break large files into small chunks,
       and allows the generated text to be streamed back to protoc so that large
       files need not reside completely in memory at one time.  Note that as of
       this writing protoc does not optimize for this -- it will read the entire
       CodeGeneratorResponse before writing files to disk.
       
      optional string name = 1;
      Returns:
      This builder for chaining.
    • setNameBytes

       The file name, relative to the output directory.  The name must not
       contain "." or ".." components and must be relative, not be absolute (so,
       the file cannot lie outside the output directory).  "/" must be used as
       the path separator, not "\".
       If the name is omitted, the content will be appended to the previous
       file.  This allows the generator to break large files into small chunks,
       and allows the generated text to be streamed back to protoc so that large
       files need not reside completely in memory at one time.  Note that as of
       this writing protoc does not optimize for this -- it will read the entire
       CodeGeneratorResponse before writing files to disk.
       
      optional string name = 1;
      Parameters:
      value - The bytes for name to set.
      Returns:
      This builder for chaining.
    • hasInsertionPoint

      public boolean hasInsertionPoint()
       If non-empty, indicates that the named file should already exist, and the
       content here is to be inserted into that file at a defined insertion
       point.  This feature allows a code generator to extend the output
       produced by another code generator.  The original generator may provide
       insertion points by placing special annotations in the file that look
       like:
         @@protoc_insertion_point(NAME)
       The annotation can have arbitrary text before and after it on the line,
       which allows it to be placed in a comment.  NAME should be replaced with
       an identifier naming the point -- this is what other generators will use
       as the insertion_point.  Code inserted at this point will be placed
       immediately above the line containing the insertion point (thus multiple
       insertions to the same point will come out in the order they were added).
       The double-@ is intended to make it unlikely that the generated code
       could contain things that look like insertion points by accident.
       For example, the C++ code generator places the following line in the
       .pb.h files that it generates:
         // @@protoc_insertion_point(namespace_scope)
       This line appears within the scope of the file's package namespace, but
       outside of any particular class.  Another plugin can then specify the
       insertion_point "namespace_scope" to generate additional classes or
       other declarations that should be placed in this scope.
       Note that if the line containing the insertion point begins with
       whitespace, the same whitespace will be added to every line of the
       inserted text.  This is useful for languages like Python, where
       indentation matters.  In these languages, the insertion point comment
       should be indented the same amount as any inserted code will need to be
       in order to work correctly in that context.
       The code generator that generates the initial file and the one which
       inserts into it must both run as part of a single invocation of protoc.
       Code generators are executed in the order in which they appear on the
       command line.
       If |insertion_point| is present, |name| must also be present.
       
      optional string insertion_point = 2;
      Specified by:
      hasInsertionPoint in interface PluginProtos.CodeGeneratorResponse.FileOrBuilder
      Returns:
      Whether the insertionPoint field is set.
    • getInsertionPoint

      public String getInsertionPoint()
       If non-empty, indicates that the named file should already exist, and the
       content here is to be inserted into that file at a defined insertion
       point.  This feature allows a code generator to extend the output
       produced by another code generator.  The original generator may provide
       insertion points by placing special annotations in the file that look
       like:
         @@protoc_insertion_point(NAME)
       The annotation can have arbitrary text before and after it on the line,
       which allows it to be placed in a comment.  NAME should be replaced with
       an identifier naming the point -- this is what other generators will use
       as the insertion_point.  Code inserted at this point will be placed
       immediately above the line containing the insertion point (thus multiple
       insertions to the same point will come out in the order they were added).
       The double-@ is intended to make it unlikely that the generated code
       could contain things that look like insertion points by accident.
       For example, the C++ code generator places the following line in the
       .pb.h files that it generates:
         // @@protoc_insertion_point(namespace_scope)
       This line appears within the scope of the file's package namespace, but
       outside of any particular class.  Another plugin can then specify the
       insertion_point "namespace_scope" to generate additional classes or
       other declarations that should be placed in this scope.
       Note that if the line containing the insertion point begins with
       whitespace, the same whitespace will be added to every line of the
       inserted text.  This is useful for languages like Python, where
       indentation matters.  In these languages, the insertion point comment
       should be indented the same amount as any inserted code will need to be
       in order to work correctly in that context.
       The code generator that generates the initial file and the one which
       inserts into it must both run as part of a single invocation of protoc.
       Code generators are executed in the order in which they appear on the
       command line.
       If |insertion_point| is present, |name| must also be present.
       
      optional string insertion_point = 2;
      Specified by:
      getInsertionPoint in interface PluginProtos.CodeGeneratorResponse.FileOrBuilder
      Returns:
      The insertionPoint.
    • getInsertionPointBytes

      public ByteString getInsertionPointBytes()
       If non-empty, indicates that the named file should already exist, and the
       content here is to be inserted into that file at a defined insertion
       point.  This feature allows a code generator to extend the output
       produced by another code generator.  The original generator may provide
       insertion points by placing special annotations in the file that look
       like:
         @@protoc_insertion_point(NAME)
       The annotation can have arbitrary text before and after it on the line,
       which allows it to be placed in a comment.  NAME should be replaced with
       an identifier naming the point -- this is what other generators will use
       as the insertion_point.  Code inserted at this point will be placed
       immediately above the line containing the insertion point (thus multiple
       insertions to the same point will come out in the order they were added).
       The double-@ is intended to make it unlikely that the generated code
       could contain things that look like insertion points by accident.
       For example, the C++ code generator places the following line in the
       .pb.h files that it generates:
         // @@protoc_insertion_point(namespace_scope)
       This line appears within the scope of the file's package namespace, but
       outside of any particular class.  Another plugin can then specify the
       insertion_point "namespace_scope" to generate additional classes or
       other declarations that should be placed in this scope.
       Note that if the line containing the insertion point begins with
       whitespace, the same whitespace will be added to every line of the
       inserted text.  This is useful for languages like Python, where
       indentation matters.  In these languages, the insertion point comment
       should be indented the same amount as any inserted code will need to be
       in order to work correctly in that context.
       The code generator that generates the initial file and the one which
       inserts into it must both run as part of a single invocation of protoc.
       Code generators are executed in the order in which they appear on the
       command line.
       If |insertion_point| is present, |name| must also be present.
       
      optional string insertion_point = 2;
      Specified by:
      getInsertionPointBytes in interface PluginProtos.CodeGeneratorResponse.FileOrBuilder
      Returns:
      The bytes for insertionPoint.
    • setInsertionPoint

      public PluginProtos.CodeGeneratorResponse.File.Builder setInsertionPoint(String value)
       If non-empty, indicates that the named file should already exist, and the
       content here is to be inserted into that file at a defined insertion
       point.  This feature allows a code generator to extend the output
       produced by another code generator.  The original generator may provide
       insertion points by placing special annotations in the file that look
       like:
         @@protoc_insertion_point(NAME)
       The annotation can have arbitrary text before and after it on the line,
       which allows it to be placed in a comment.  NAME should be replaced with
       an identifier naming the point -- this is what other generators will use
       as the insertion_point.  Code inserted at this point will be placed
       immediately above the line containing the insertion point (thus multiple
       insertions to the same point will come out in the order they were added).
       The double-@ is intended to make it unlikely that the generated code
       could contain things that look like insertion points by accident.
       For example, the C++ code generator places the following line in the
       .pb.h files that it generates:
         // @@protoc_insertion_point(namespace_scope)
       This line appears within the scope of the file's package namespace, but
       outside of any particular class.  Another plugin can then specify the
       insertion_point "namespace_scope" to generate additional classes or
       other declarations that should be placed in this scope.
       Note that if the line containing the insertion point begins with
       whitespace, the same whitespace will be added to every line of the
       inserted text.  This is useful for languages like Python, where
       indentation matters.  In these languages, the insertion point comment
       should be indented the same amount as any inserted code will need to be
       in order to work correctly in that context.
       The code generator that generates the initial file and the one which
       inserts into it must both run as part of a single invocation of protoc.
       Code generators are executed in the order in which they appear on the
       command line.
       If |insertion_point| is present, |name| must also be present.
       
      optional string insertion_point = 2;
      Parameters:
      value - The insertionPoint to set.
      Returns:
      This builder for chaining.
    • clearInsertionPoint

       If non-empty, indicates that the named file should already exist, and the
       content here is to be inserted into that file at a defined insertion
       point.  This feature allows a code generator to extend the output
       produced by another code generator.  The original generator may provide
       insertion points by placing special annotations in the file that look
       like:
         @@protoc_insertion_point(NAME)
       The annotation can have arbitrary text before and after it on the line,
       which allows it to be placed in a comment.  NAME should be replaced with
       an identifier naming the point -- this is what other generators will use
       as the insertion_point.  Code inserted at this point will be placed
       immediately above the line containing the insertion point (thus multiple
       insertions to the same point will come out in the order they were added).
       The double-@ is intended to make it unlikely that the generated code
       could contain things that look like insertion points by accident.
       For example, the C++ code generator places the following line in the
       .pb.h files that it generates:
         // @@protoc_insertion_point(namespace_scope)
       This line appears within the scope of the file's package namespace, but
       outside of any particular class.  Another plugin can then specify the
       insertion_point "namespace_scope" to generate additional classes or
       other declarations that should be placed in this scope.
       Note that if the line containing the insertion point begins with
       whitespace, the same whitespace will be added to every line of the
       inserted text.  This is useful for languages like Python, where
       indentation matters.  In these languages, the insertion point comment
       should be indented the same amount as any inserted code will need to be
       in order to work correctly in that context.
       The code generator that generates the initial file and the one which
       inserts into it must both run as part of a single invocation of protoc.
       Code generators are executed in the order in which they appear on the
       command line.
       If |insertion_point| is present, |name| must also be present.
       
      optional string insertion_point = 2;
      Returns:
      This builder for chaining.
    • setInsertionPointBytes

      public PluginProtos.CodeGeneratorResponse.File.Builder setInsertionPointBytes(ByteString value)
       If non-empty, indicates that the named file should already exist, and the
       content here is to be inserted into that file at a defined insertion
       point.  This feature allows a code generator to extend the output
       produced by another code generator.  The original generator may provide
       insertion points by placing special annotations in the file that look
       like:
         @@protoc_insertion_point(NAME)
       The annotation can have arbitrary text before and after it on the line,
       which allows it to be placed in a comment.  NAME should be replaced with
       an identifier naming the point -- this is what other generators will use
       as the insertion_point.  Code inserted at this point will be placed
       immediately above the line containing the insertion point (thus multiple
       insertions to the same point will come out in the order they were added).
       The double-@ is intended to make it unlikely that the generated code
       could contain things that look like insertion points by accident.
       For example, the C++ code generator places the following line in the
       .pb.h files that it generates:
         // @@protoc_insertion_point(namespace_scope)
       This line appears within the scope of the file's package namespace, but
       outside of any particular class.  Another plugin can then specify the
       insertion_point "namespace_scope" to generate additional classes or
       other declarations that should be placed in this scope.
       Note that if the line containing the insertion point begins with
       whitespace, the same whitespace will be added to every line of the
       inserted text.  This is useful for languages like Python, where
       indentation matters.  In these languages, the insertion point comment
       should be indented the same amount as any inserted code will need to be
       in order to work correctly in that context.
       The code generator that generates the initial file and the one which
       inserts into it must both run as part of a single invocation of protoc.
       Code generators are executed in the order in which they appear on the
       command line.
       If |insertion_point| is present, |name| must also be present.
       
      optional string insertion_point = 2;
      Parameters:
      value - The bytes for insertionPoint to set.
      Returns:
      This builder for chaining.
    • hasContent

      public boolean hasContent()
       The file contents.
       
      optional string content = 15;
      Specified by:
      hasContent in interface PluginProtos.CodeGeneratorResponse.FileOrBuilder
      Returns:
      Whether the content field is set.
    • getContent

      public String getContent()
       The file contents.
       
      optional string content = 15;
      Specified by:
      getContent in interface PluginProtos.CodeGeneratorResponse.FileOrBuilder
      Returns:
      The content.
    • getContentBytes

      public ByteString getContentBytes()
       The file contents.
       
      optional string content = 15;
      Specified by:
      getContentBytes in interface PluginProtos.CodeGeneratorResponse.FileOrBuilder
      Returns:
      The bytes for content.
    • setContent

       The file contents.
       
      optional string content = 15;
      Parameters:
      value - The content to set.
      Returns:
      This builder for chaining.
    • clearContent

       The file contents.
       
      optional string content = 15;
      Returns:
      This builder for chaining.
    • setContentBytes

       The file contents.
       
      optional string content = 15;
      Parameters:
      value - The bytes for content to set.
      Returns:
      This builder for chaining.
    • hasGeneratedCodeInfo

      public boolean hasGeneratedCodeInfo()
       Information describing the file content being inserted. If an insertion
       point is used, this information will be appropriately offset and inserted
       into the code generation metadata for the generated files.
       
      optional .google.protobuf.GeneratedCodeInfo generated_code_info = 16;
      Specified by:
      hasGeneratedCodeInfo in interface PluginProtos.CodeGeneratorResponse.FileOrBuilder
      Returns:
      Whether the generatedCodeInfo field is set.
    • getGeneratedCodeInfo

      public DescriptorProtos.GeneratedCodeInfo getGeneratedCodeInfo()
       Information describing the file content being inserted. If an insertion
       point is used, this information will be appropriately offset and inserted
       into the code generation metadata for the generated files.
       
      optional .google.protobuf.GeneratedCodeInfo generated_code_info = 16;
      Specified by:
      getGeneratedCodeInfo in interface PluginProtos.CodeGeneratorResponse.FileOrBuilder
      Returns:
      The generatedCodeInfo.
    • setGeneratedCodeInfo

       Information describing the file content being inserted. If an insertion
       point is used, this information will be appropriately offset and inserted
       into the code generation metadata for the generated files.
       
      optional .google.protobuf.GeneratedCodeInfo generated_code_info = 16;
    • setGeneratedCodeInfo

       Information describing the file content being inserted. If an insertion
       point is used, this information will be appropriately offset and inserted
       into the code generation metadata for the generated files.
       
      optional .google.protobuf.GeneratedCodeInfo generated_code_info = 16;
    • mergeGeneratedCodeInfo

       Information describing the file content being inserted. If an insertion
       point is used, this information will be appropriately offset and inserted
       into the code generation metadata for the generated files.
       
      optional .google.protobuf.GeneratedCodeInfo generated_code_info = 16;
    • clearGeneratedCodeInfo

      public PluginProtos.CodeGeneratorResponse.File.Builder clearGeneratedCodeInfo()
       Information describing the file content being inserted. If an insertion
       point is used, this information will be appropriately offset and inserted
       into the code generation metadata for the generated files.
       
      optional .google.protobuf.GeneratedCodeInfo generated_code_info = 16;
    • getGeneratedCodeInfoBuilder

      public DescriptorProtos.GeneratedCodeInfo.Builder getGeneratedCodeInfoBuilder()
       Information describing the file content being inserted. If an insertion
       point is used, this information will be appropriately offset and inserted
       into the code generation metadata for the generated files.
       
      optional .google.protobuf.GeneratedCodeInfo generated_code_info = 16;
    • getGeneratedCodeInfoOrBuilder

      public DescriptorProtos.GeneratedCodeInfoOrBuilder getGeneratedCodeInfoOrBuilder()
       Information describing the file content being inserted. If an insertion
       point is used, this information will be appropriately offset and inserted
       into the code generation metadata for the generated files.
       
      optional .google.protobuf.GeneratedCodeInfo generated_code_info = 16;
      Specified by:
      getGeneratedCodeInfoOrBuilder in interface PluginProtos.CodeGeneratorResponse.FileOrBuilder
    • getGeneratedCodeInfoFieldBuilder

       Information describing the file content being inserted. If an insertion
       point is used, this information will be appropriately offset and inserted
       into the code generation metadata for the generated files.
       
      optional .google.protobuf.GeneratedCodeInfo generated_code_info = 16;
    • setUnknownFields

      public final PluginProtos.CodeGeneratorResponse.File.Builder setUnknownFields(UnknownFieldSet unknownFields)
      Description copied from interface: Message.Builder
      Set the UnknownFieldSet for this message.
      Specified by:
      setUnknownFields in interface Message.Builder
      Overrides:
      setUnknownFields in class GeneratedMessageV3.Builder<PluginProtos.CodeGeneratorResponse.File.Builder>
    • mergeUnknownFields

      public final PluginProtos.CodeGeneratorResponse.File.Builder mergeUnknownFields(UnknownFieldSet unknownFields)
      Description copied from interface: Message.Builder
      Merge some unknown fields into the UnknownFieldSet for this message.
      Specified by:
      mergeUnknownFields in interface Message.Builder
      Overrides:
      mergeUnknownFields in class GeneratedMessageV3.Builder<PluginProtos.CodeGeneratorResponse.File.Builder>