PluginProtos.CodeGeneratorResponse.File.Builder (Protocol Buffers [Kotlin-Core] 3.20.3 API)

java.lang.Object
- com.google.protobuf.AbstractMessageLite.Builder
- - com.google.protobuf.AbstractMessage.Builder<BuilderType>
  - - com.google.protobuf.GeneratedMessageV3.Builder<PluginProtos.CodeGeneratorResponse.File.Builder>
    - - com.google.protobuf.compiler.PluginProtos.CodeGeneratorResponse.File.Builder

All Implemented Interfaces:

PluginProtos.CodeGeneratorResponse.FileOrBuilder, com.google.protobuf.Message.Builder, com.google.protobuf.MessageLite.Builder, com.google.protobuf.MessageLiteOrBuilder, com.google.protobuf.MessageOrBuilder, Cloneable

Enclosing class:

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

Method Summary

All Methods Static Methods Instance Methods Concrete Methods
Modifier and Type	Method and Description
`PluginProtos.CodeGeneratorResponse.File.Builder`	`addRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field, Object value)`
`PluginProtos.CodeGeneratorResponse.File`	`build()`
`PluginProtos.CodeGeneratorResponse.File`	`buildPartial()`
`PluginProtos.CodeGeneratorResponse.File.Builder`	`clear()`
`PluginProtos.CodeGeneratorResponse.File.Builder`	`clearContent()` The file contents.
`PluginProtos.CodeGeneratorResponse.File.Builder`	`clearField(com.google.protobuf.Descriptors.FieldDescriptor field)`
`PluginProtos.CodeGeneratorResponse.File.Builder`	`clearGeneratedCodeInfo()` Information describing the file content being inserted.
`PluginProtos.CodeGeneratorResponse.File.Builder`	`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.
`PluginProtos.CodeGeneratorResponse.File.Builder`	`clearName()` The file name, relative to the output directory.
`PluginProtos.CodeGeneratorResponse.File.Builder`	`clearOneof(com.google.protobuf.Descriptors.OneofDescriptor oneof)`
`PluginProtos.CodeGeneratorResponse.File.Builder`	`clone()`
`String`	`getContent()` The file contents.
`com.google.protobuf.ByteString`	`getContentBytes()` The file contents.
`PluginProtos.CodeGeneratorResponse.File`	`getDefaultInstanceForType()`
`static com.google.protobuf.Descriptors.Descriptor`	`getDescriptor()`
`com.google.protobuf.Descriptors.Descriptor`	`getDescriptorForType()`
`DescriptorProtos.GeneratedCodeInfo`	`getGeneratedCodeInfo()` Information describing the file content being inserted.
`DescriptorProtos.GeneratedCodeInfo.Builder`	`getGeneratedCodeInfoBuilder()` Information describing the file content being inserted.
`DescriptorProtos.GeneratedCodeInfoOrBuilder`	`getGeneratedCodeInfoOrBuilder()` Information describing the file content being inserted.
`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.
`com.google.protobuf.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.
`String`	`getName()` The file name, relative to the output directory.
`com.google.protobuf.ByteString`	`getNameBytes()` The file name, relative to the output directory.
`boolean`	`hasContent()` The file contents.
`boolean`	`hasGeneratedCodeInfo()` Information describing the file content being inserted.
`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.
`boolean`	`hasName()` The file name, relative to the output directory.
`protected com.google.protobuf.GeneratedMessageV3.FieldAccessorTable`	`internalGetFieldAccessorTable()`
`boolean`	`isInitialized()`
`PluginProtos.CodeGeneratorResponse.File.Builder`	`mergeFrom(com.google.protobuf.CodedInputStream input, com.google.protobuf.ExtensionRegistryLite extensionRegistry)`
`PluginProtos.CodeGeneratorResponse.File.Builder`	`mergeFrom(com.google.protobuf.Message other)`
`PluginProtos.CodeGeneratorResponse.File.Builder`	`mergeFrom(PluginProtos.CodeGeneratorResponse.File other)`
`PluginProtos.CodeGeneratorResponse.File.Builder`	`mergeGeneratedCodeInfo(DescriptorProtos.GeneratedCodeInfo value)` Information describing the file content being inserted.
`PluginProtos.CodeGeneratorResponse.File.Builder`	`mergeUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields)`
`PluginProtos.CodeGeneratorResponse.File.Builder`	`setContent(String value)` The file contents.
`PluginProtos.CodeGeneratorResponse.File.Builder`	`setContentBytes(com.google.protobuf.ByteString value)` The file contents.
`PluginProtos.CodeGeneratorResponse.File.Builder`	`setField(com.google.protobuf.Descriptors.FieldDescriptor field, Object value)`
`PluginProtos.CodeGeneratorResponse.File.Builder`	`setGeneratedCodeInfo(DescriptorProtos.GeneratedCodeInfo.Builder builderForValue)` Information describing the file content being inserted.
`PluginProtos.CodeGeneratorResponse.File.Builder`	`setGeneratedCodeInfo(DescriptorProtos.GeneratedCodeInfo value)` Information describing the file content being inserted.
`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.
`PluginProtos.CodeGeneratorResponse.File.Builder`	`setInsertionPointBytes(com.google.protobuf.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.
`PluginProtos.CodeGeneratorResponse.File.Builder`	`setName(String value)` The file name, relative to the output directory.
`PluginProtos.CodeGeneratorResponse.File.Builder`	`setNameBytes(com.google.protobuf.ByteString value)` The file name, relative to the output directory.
`PluginProtos.CodeGeneratorResponse.File.Builder`	`setRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field, int index, Object value)`
`PluginProtos.CodeGeneratorResponse.File.Builder`	`setUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields)`

Methods inherited from class com.google.protobuf.GeneratedMessageV3.Builder
getAllFields, getField, getFieldBuilder, getOneofFieldDescriptor, getParentForChildren, getRepeatedField, getRepeatedFieldBuilder, getRepeatedFieldCount, getUnknownFields, getUnknownFieldSetBuilder, hasField, hasOneof, internalGetMapField, internalGetMutableMapField, isClean, markClean, mergeUnknownLengthDelimitedField, mergeUnknownVarintField, newBuilderForField, onBuilt, onChanged, parseUnknownField, setUnknownFieldSetBuilder, setUnknownFieldsProto3

Methods inherited from class com.google.protobuf.AbstractMessage.Builder
findInitializationErrors, getInitializationErrorString, internalMergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, newUninitializedMessageException, toString

Methods inherited from class com.google.protobuf.AbstractMessageLite.Builder
addAll, addAll, mergeDelimitedFrom, mergeDelimitedFrom, mergeFrom, newUninitializedMessageException

Methods inherited from class java.lang.Object
equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait

Methods inherited from interface com.google.protobuf.MessageOrBuilder
findInitializationErrors, getAllFields, getField, getInitializationErrorString, getOneofFieldDescriptor, getRepeatedField, getRepeatedFieldCount, getUnknownFields, hasField, hasOneof

Methods inherited from interface com.google.protobuf.Message.Builder
mergeDelimitedFrom, mergeDelimitedFrom

Methods inherited from interface com.google.protobuf.MessageLite.Builder
mergeFrom

Method Detail

getDescriptor

public static final com.google.protobuf.Descriptors.Descriptor getDescriptor()

internalGetFieldAccessorTable
```
protected com.google.protobuf.GeneratedMessageV3.FieldAccessorTable internalGetFieldAccessorTable()
```
Specified by:

internalGetFieldAccessorTable in class com.google.protobuf.GeneratedMessageV3.Builder<PluginProtos.CodeGeneratorResponse.File.Builder>

clear
```
public PluginProtos.CodeGeneratorResponse.File.Builder clear()
```
Specified by:

clear in interface com.google.protobuf.Message.Builder

Specified by:

clear in interface com.google.protobuf.MessageLite.Builder

Overrides:

clear in class com.google.protobuf.GeneratedMessageV3.Builder<PluginProtos.CodeGeneratorResponse.File.Builder>

getDescriptorForType
```
public com.google.protobuf.Descriptors.Descriptor getDescriptorForType()
```
Specified by:

getDescriptorForType in interface com.google.protobuf.Message.Builder

Specified by:

getDescriptorForType in interface com.google.protobuf.MessageOrBuilder

Overrides:

getDescriptorForType in class com.google.protobuf.GeneratedMessageV3.Builder<PluginProtos.CodeGeneratorResponse.File.Builder>

getDefaultInstanceForType
```
public PluginProtos.CodeGeneratorResponse.File getDefaultInstanceForType()
```
Specified by:

getDefaultInstanceForType in interface com.google.protobuf.MessageLiteOrBuilder

Specified by:

getDefaultInstanceForType in interface com.google.protobuf.MessageOrBuilder

build
```
public PluginProtos.CodeGeneratorResponse.File build()
```
Specified by:

build in interface com.google.protobuf.Message.Builder

Specified by:

build in interface com.google.protobuf.MessageLite.Builder

buildPartial
```
public PluginProtos.CodeGeneratorResponse.File buildPartial()
```
Specified by:

buildPartial in interface com.google.protobuf.Message.Builder

Specified by:

buildPartial in interface com.google.protobuf.MessageLite.Builder

clone
```
public PluginProtos.CodeGeneratorResponse.File.Builder clone()
```
Specified by:

clone in interface com.google.protobuf.Message.Builder

Specified by:

clone in interface com.google.protobuf.MessageLite.Builder

Overrides:

clone in class com.google.protobuf.GeneratedMessageV3.Builder<PluginProtos.CodeGeneratorResponse.File.Builder>

setField

public PluginProtos.CodeGeneratorResponse.File.Builder setField(com.google.protobuf.Descriptors.FieldDescriptor field,
                                                                Object value)

Specified by:: setField in interface com.google.protobuf.Message.Builder
Overrides:: setField in class com.google.protobuf.GeneratedMessageV3.Builder<PluginProtos.CodeGeneratorResponse.File.Builder>

clearField
```
public PluginProtos.CodeGeneratorResponse.File.Builder clearField(com.google.protobuf.Descriptors.FieldDescriptor field)
```
Specified by:

clearField in interface com.google.protobuf.Message.Builder

Overrides:

clearField in class com.google.protobuf.GeneratedMessageV3.Builder<PluginProtos.CodeGeneratorResponse.File.Builder>

clearOneof
```
public PluginProtos.CodeGeneratorResponse.File.Builder clearOneof(com.google.protobuf.Descriptors.OneofDescriptor oneof)
```
Specified by:

clearOneof in interface com.google.protobuf.Message.Builder

Overrides:

clearOneof in class com.google.protobuf.GeneratedMessageV3.Builder<PluginProtos.CodeGeneratorResponse.File.Builder>

setRepeatedField

public PluginProtos.CodeGeneratorResponse.File.Builder setRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field,
                                                                        int index,
                                                                        Object value)

Specified by:: setRepeatedField in interface com.google.protobuf.Message.Builder
Overrides:: setRepeatedField in class com.google.protobuf.GeneratedMessageV3.Builder<PluginProtos.CodeGeneratorResponse.File.Builder>

addRepeatedField

public PluginProtos.CodeGeneratorResponse.File.Builder addRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field,
                                                                        Object value)

Specified by:: addRepeatedField in interface com.google.protobuf.Message.Builder
Overrides:: addRepeatedField in class com.google.protobuf.GeneratedMessageV3.Builder<PluginProtos.CodeGeneratorResponse.File.Builder>

mergeFrom
```
public PluginProtos.CodeGeneratorResponse.File.Builder mergeFrom(com.google.protobuf.Message other)
```
Specified by:

mergeFrom in interface com.google.protobuf.Message.Builder

Overrides:

mergeFrom in class com.google.protobuf.AbstractMessage.Builder<PluginProtos.CodeGeneratorResponse.File.Builder>

mergeFrom

public PluginProtos.CodeGeneratorResponse.File.Builder mergeFrom(PluginProtos.CodeGeneratorResponse.File other)

isInitialized
```
public final boolean isInitialized()
```
Specified by:

isInitialized in interface com.google.protobuf.MessageLiteOrBuilder

Overrides:

isInitialized in class com.google.protobuf.GeneratedMessageV3.Builder<PluginProtos.CodeGeneratorResponse.File.Builder>

mergeFrom

public PluginProtos.CodeGeneratorResponse.File.Builder mergeFrom(com.google.protobuf.CodedInputStream input,
                                                                 com.google.protobuf.ExtensionRegistryLite extensionRegistry)
                                                          throws IOException

Specified by:: mergeFrom in interface com.google.protobuf.Message.Builder
Specified by:: mergeFrom in interface com.google.protobuf.MessageLite.Builder
Overrides:: mergeFrom in class com.google.protobuf.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 com.google.protobuf.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

public PluginProtos.CodeGeneratorResponse.File.Builder setName(String value)

 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

public PluginProtos.CodeGeneratorResponse.File.Builder 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

public PluginProtos.CodeGeneratorResponse.File.Builder setNameBytes(com.google.protobuf.ByteString value)

 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 com.google.protobuf.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

public PluginProtos.CodeGeneratorResponse.File.Builder 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(com.google.protobuf.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 com.google.protobuf.ByteString getContentBytes()
```
```
 The file contents.
 
```
optional string content = 15;
Specified by:

getContentBytes in interface PluginProtos.CodeGeneratorResponse.FileOrBuilder

Returns:

The bytes for content.

setContent

public PluginProtos.CodeGeneratorResponse.File.Builder setContent(String value)

 The file contents.

optional string content = 15;

Parameters:: value - The content to set.
Returns:: This builder for chaining.

clearContent

public PluginProtos.CodeGeneratorResponse.File.Builder clearContent()

 The file contents.

optional string content = 15;

Returns:: This builder for chaining.

setContentBytes

public PluginProtos.CodeGeneratorResponse.File.Builder setContentBytes(com.google.protobuf.ByteString value)

 The file contents.

optional string content = 15;

Parameters:: value - The bytes for content to set.
Returns:: This builder for chaining.