pub struct File {
    pub name: Option<String>,
    pub insertion_point: Option<String>,
    pub content: Option<String>,
    pub generated_code_info: MessageField<GeneratedCodeInfo>,
    pub special_fields: SpecialFields,
}
Expand description

Represents a single generated file.

Fields

name: Option<String>

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.

insertion_point: Option<String>

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.

content: Option<String>

The file contents.

generated_code_info: MessageField<GeneratedCodeInfo>

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.

special_fields: SpecialFields

Implementations

Trait Implementations

Returns a copy of the value. Read more
Performs copy-assignment from source. Read more
Formats the value using the given formatter. Read more
Returns the “default value” for a type. Read more
Returns the “default value” for a type. Read more
Formats the value using the given formatter. Read more
Message name as specified in .proto file. Read more
True iff all required fields are initialized. Always returns true for protobuf 3. Read more
Update this message object with fields read from given stream.
Compute and cache size of this message and all nested messages. Read more
Write message to the stream. Read more
Special fields (unknown fields and cached size).
Special fields (unknown fields and cached size).
Create an empty message object. Read more
Reset all fields.
Return a pointer to default immutable message with static lifetime. Read more
Parse message from stream.
Get size previously computed by compute_size. Read more
Write the message to the stream. Read more
Write the message to the stream prepending the message with message length encoded as varint. Read more
Write the message to the vec, prepend the message with message length encoded as varint. Read more
Update this message object with fields read from given stream.
Parse message from reader. Parse stops on EOF or when error encountered. Read more
Parse message from byte array.
Parse message from Bytes object. Resulting message may share references to the passed bytes object. Read more
Check if all required fields of this object are initialized.
Write the message to the writer.
Write the message to bytes vec.
Write the message to bytes vec. Read more
Write the message to the writer, prepend the message with message length encoded as varint. Read more
Write the message to the bytes vec, prepend the message with message length encoded as varint. Read more
Get a reference to unknown fields.
Get a mutable reference to unknown fields.
Get message descriptor for message type. Read more
Reflective equality. Read more
This method tests for self and other values to be equal, and is used by ==. Read more
This method tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason. Read more
Actual implementation of type properties.

Auto Trait Implementations

Blanket Implementations

Gets the TypeId of self. Read more
Immutably borrows from an owned value. Read more
Mutably borrows from an owned value. Read more

Returns the argument unchanged.

Calls U::from(self).

That is, this conversion is whatever the implementation of From<T> for U chooses to do.

The resulting type after obtaining ownership.
Creates owned data from borrowed data, usually by cloning. Read more
Uses borrowed data to replace owned data, usually by cloning. Read more
Converts the given value to a String. Read more
The type returned in the event of a conversion error.
Performs the conversion.
The type returned in the event of a conversion error.
Performs the conversion.