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| Modifier and Type | Method and Description |
|---|---|
PluginProtos.CodeGeneratorResponse.File.Builder |
addRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field,
java.lang.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 |
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() |
java.lang.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() |
java.lang.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.
|
java.lang.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 |
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 |
mergeUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields) |
PluginProtos.CodeGeneratorResponse.File.Builder |
setContent(java.lang.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,
java.lang.Object value) |
PluginProtos.CodeGeneratorResponse.File.Builder |
setInsertionPoint(java.lang.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(java.lang.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,
java.lang.Object value) |
PluginProtos.CodeGeneratorResponse.File.Builder |
setUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields) |
getAllFields, getField, getFieldBuilder, getOneofFieldDescriptor, getParentForChildren, getRepeatedField, getRepeatedFieldBuilder, getRepeatedFieldCount, getUnknownFields, hasField, hasOneof, internalGetMapField, internalGetMutableMapField, isClean, markClean, newBuilderForField, onBuilt, onChanged, setUnknownFieldsProto3findInitializationErrors, getInitializationErrorString, internalMergeFrom, mergeDelimitedFrom, mergeDelimitedFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, newUninitializedMessageException, toStringaddAll, addAll, mergeFrom, newUninitializedMessageExceptionequals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, waitpublic static final com.google.protobuf.Descriptors.Descriptor getDescriptor()
protected com.google.protobuf.GeneratedMessageV3.FieldAccessorTable internalGetFieldAccessorTable()
internalGetFieldAccessorTable in class com.google.protobuf.GeneratedMessageV3.Builder<PluginProtos.CodeGeneratorResponse.File.Builder>public PluginProtos.CodeGeneratorResponse.File.Builder clear()
clear in interface com.google.protobuf.Message.Builderclear in interface com.google.protobuf.MessageLite.Builderclear in class com.google.protobuf.GeneratedMessageV3.Builder<PluginProtos.CodeGeneratorResponse.File.Builder>public com.google.protobuf.Descriptors.Descriptor getDescriptorForType()
getDescriptorForType in interface com.google.protobuf.Message.BuildergetDescriptorForType in interface com.google.protobuf.MessageOrBuildergetDescriptorForType in class com.google.protobuf.GeneratedMessageV3.Builder<PluginProtos.CodeGeneratorResponse.File.Builder>public PluginProtos.CodeGeneratorResponse.File getDefaultInstanceForType()
getDefaultInstanceForType in interface com.google.protobuf.MessageLiteOrBuildergetDefaultInstanceForType in interface com.google.protobuf.MessageOrBuilderpublic PluginProtos.CodeGeneratorResponse.File build()
build in interface com.google.protobuf.Message.Builderbuild in interface com.google.protobuf.MessageLite.Builderpublic PluginProtos.CodeGeneratorResponse.File buildPartial()
buildPartial in interface com.google.protobuf.Message.BuilderbuildPartial in interface com.google.protobuf.MessageLite.Builderpublic PluginProtos.CodeGeneratorResponse.File.Builder clone()
clone in interface com.google.protobuf.Message.Builderclone in interface com.google.protobuf.MessageLite.Builderclone in class com.google.protobuf.GeneratedMessageV3.Builder<PluginProtos.CodeGeneratorResponse.File.Builder>public PluginProtos.CodeGeneratorResponse.File.Builder setField(com.google.protobuf.Descriptors.FieldDescriptor field, java.lang.Object value)
setField in interface com.google.protobuf.Message.BuildersetField in class com.google.protobuf.GeneratedMessageV3.Builder<PluginProtos.CodeGeneratorResponse.File.Builder>public PluginProtos.CodeGeneratorResponse.File.Builder clearField(com.google.protobuf.Descriptors.FieldDescriptor field)
clearField in interface com.google.protobuf.Message.BuilderclearField in class com.google.protobuf.GeneratedMessageV3.Builder<PluginProtos.CodeGeneratorResponse.File.Builder>public PluginProtos.CodeGeneratorResponse.File.Builder clearOneof(com.google.protobuf.Descriptors.OneofDescriptor oneof)
clearOneof in interface com.google.protobuf.Message.BuilderclearOneof in class com.google.protobuf.GeneratedMessageV3.Builder<PluginProtos.CodeGeneratorResponse.File.Builder>public PluginProtos.CodeGeneratorResponse.File.Builder setRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field, int index, java.lang.Object value)
setRepeatedField in interface com.google.protobuf.Message.BuildersetRepeatedField in class com.google.protobuf.GeneratedMessageV3.Builder<PluginProtos.CodeGeneratorResponse.File.Builder>public PluginProtos.CodeGeneratorResponse.File.Builder addRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field, java.lang.Object value)
addRepeatedField in interface com.google.protobuf.Message.BuilderaddRepeatedField in class com.google.protobuf.GeneratedMessageV3.Builder<PluginProtos.CodeGeneratorResponse.File.Builder>public PluginProtos.CodeGeneratorResponse.File.Builder mergeFrom(com.google.protobuf.Message other)
mergeFrom in interface com.google.protobuf.Message.BuildermergeFrom in class com.google.protobuf.AbstractMessage.Builder<PluginProtos.CodeGeneratorResponse.File.Builder>public PluginProtos.CodeGeneratorResponse.File.Builder mergeFrom(PluginProtos.CodeGeneratorResponse.File other)
public final boolean isInitialized()
isInitialized in interface com.google.protobuf.MessageLiteOrBuilderisInitialized in class com.google.protobuf.GeneratedMessageV3.Builder<PluginProtos.CodeGeneratorResponse.File.Builder>public PluginProtos.CodeGeneratorResponse.File.Builder mergeFrom(com.google.protobuf.CodedInputStream input, com.google.protobuf.ExtensionRegistryLite extensionRegistry) throws java.io.IOException
mergeFrom in interface com.google.protobuf.Message.BuildermergeFrom in interface com.google.protobuf.MessageLite.BuildermergeFrom in class com.google.protobuf.AbstractMessage.Builder<PluginProtos.CodeGeneratorResponse.File.Builder>java.io.IOExceptionpublic 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;hasName in interface PluginProtos.CodeGeneratorResponse.FileOrBuilderpublic java.lang.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;getName in interface PluginProtos.CodeGeneratorResponse.FileOrBuilderpublic 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;getNameBytes in interface PluginProtos.CodeGeneratorResponse.FileOrBuilderpublic PluginProtos.CodeGeneratorResponse.File.Builder setName(java.lang.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;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;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;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;hasInsertionPoint in interface PluginProtos.CodeGeneratorResponse.FileOrBuilderpublic java.lang.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;getInsertionPoint in interface PluginProtos.CodeGeneratorResponse.FileOrBuilderpublic 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;getInsertionPointBytes in interface PluginProtos.CodeGeneratorResponse.FileOrBuilderpublic PluginProtos.CodeGeneratorResponse.File.Builder setInsertionPoint(java.lang.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;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;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;public boolean hasContent()
The file contents.
optional string content = 15;hasContent in interface PluginProtos.CodeGeneratorResponse.FileOrBuilderpublic java.lang.String getContent()
The file contents.
optional string content = 15;getContent in interface PluginProtos.CodeGeneratorResponse.FileOrBuilderpublic com.google.protobuf.ByteString getContentBytes()
The file contents.
optional string content = 15;getContentBytes in interface PluginProtos.CodeGeneratorResponse.FileOrBuilderpublic PluginProtos.CodeGeneratorResponse.File.Builder setContent(java.lang.String value)
The file contents.
optional string content = 15;public PluginProtos.CodeGeneratorResponse.File.Builder clearContent()
The file contents.
optional string content = 15;public PluginProtos.CodeGeneratorResponse.File.Builder setContentBytes(com.google.protobuf.ByteString value)
The file contents.
optional string content = 15;public final PluginProtos.CodeGeneratorResponse.File.Builder setUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields)
setUnknownFields in interface com.google.protobuf.Message.BuildersetUnknownFields in class com.google.protobuf.GeneratedMessageV3.Builder<PluginProtos.CodeGeneratorResponse.File.Builder>public final PluginProtos.CodeGeneratorResponse.File.Builder mergeUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields)
mergeUnknownFields in interface com.google.protobuf.Message.BuildermergeUnknownFields in class com.google.protobuf.GeneratedMessageV3.Builder<PluginProtos.CodeGeneratorResponse.File.Builder>