protoreflect: Index | Files

package protoprint

import ""

Package protoprint provides a mechanism to generate protobuf source code from descriptors.

This can be useful to turn file descriptor sets (produced by protoc) back into proto IDL code. Combined with the protoreflect/builder package, it can also be used to perform code generation of proto source code.


Package Files

doc.go print.go

type CommentType Uses

type CommentType int

CommentType is a kind of comments in a proto source file. This can be used as a bitmask.

const (
    // CommentsDetached refers to comments that are not "attached" to any
    // source element. They are attributed to the subsequent element in the
    // file as "detached" comments.
    CommentsDetached CommentType = 1 << iota
    // CommentsTrailing refers to a comment block immediately following an
    // element in the source file. If another element immediately follows
    // the trailing comment, it is instead considered a leading comment for
    // that subsequent element.
    // CommentsLeading refers to a comment block immediately preceding an
    // element in the source file. For high-level elements (those that have
    // their own descriptor), these are used as doc comments for that element.
    // CommentsTokens refers to any comments (leading, trailing, or detached)
    // on low-level elements in the file. "High-level" elements have their own
    // descriptors, e.g. messages, enums, fields, services, and methods. But
    // comments can appear anywhere (such as around identifiers and keywords,
    // sprinkled inside the declarations of a high-level element). This class
    // of comments are for those extra comments sprinkled into the file.

    // CommentsNonDoc refers to comments that are *not* doc comments. This is a
    // bitwise union of everything other than CommentsLeading. If you configure
    // a printer to omit this, only doc comments on descriptor elements will be
    // included in the printed output.
    CommentsNonDoc = CommentsDetached | CommentsTrailing | CommentsTokens
    // CommentsAll indicates all kinds of comments. If you configure a printer
    // to omit this, no comments will appear in the printed output, even if the
    // input descriptors had source info and comments.
    CommentsAll = -1

type Printer Uses

type Printer struct {
    // If true, comments are rendered using "/*" style comments. Otherwise, they
    // are printed using "//" style line comments.
    PreferMultiLineStyleComments bool

    // If true, elements are sorted into a canonical order.
    // The canonical order for elements in a file follows:
    //  1. Syntax
    //  2. Package
    //  3. Imports (sorted lexically)
    //  4. Options (sorted by name, standard options before custom options)
    //  5. Messages (sorted by name)
    //  6. Enums (sorted by name)
    //  7. Services (sorted by name)
    //  8. Extensions (grouped by extendee, sorted by extendee+tag)
    // The canonical order of elements in a message follows:
    //  1. Options (sorted by name, standard options before custom options)
    //  2. Fields and One-Ofs (sorted by tag; one-ofs interleaved based on the
    //     minimum tag therein)
    //  3. Nested Messages (sorted by name)
    //  4. Nested Enums (sorted by name)
    //  5. Extension ranges (sorted by starting tag number)
    //  6. Nested Extensions (grouped by extendee, sorted by extendee+tag)
    //  7. Reserved ranges (sorted by starting tag number)
    //  8. Reserved names (sorted lexically)
    // Methods are sorted within a service by name and appear after any service
    // options (which are sorted by name, standard options before custom ones).
    // Enum values are sorted within an enum, first by numeric value then by
    // name, and also appear after any enum options.
    // Options for fields, enum values, and extension ranges are sorted by name,
    // standard options before custom ones.
    SortElements bool

    // The indentation used. Any characters other than spaces or tabs will be
    // replaced with spaces. If unset/empty, two spaces will be used.
    Indent string

    // If true, detached comments (between elements) will be ignored.
    // Deprecated: Use OmitComments bitmask instead.
    OmitDetachedComments bool

    // A bitmask of comment types to omit. If unset, all comments will be
    // included. Use CommentsAll to not print any comments.
    OmitComments CommentType

    // If true, trailing comments that typically appear on the same line as an
    // element (option, field, enum value, method) will be printed on a separate
    // line instead.
    // So, with this set, you'll get output like so:
    //    // leading comment for field
    //    repeated string names = 1;
    //    // trailing comment
    // If left false, the printer will try to emit trailing comments on the same
    // line instead:
    //    // leading comment for field
    //    repeated string names = 1; // trailing comment
    // If the trailing comment has more than one line, it will automatically be
    // forced to the next line. Also, elements that end with "}" instead of ";"
    // will have trailing comments rendered on the subsequent line.
    TrailingCommentsOnSeparateLine bool

    // If true, the printed output will eschew any blank lines, which otherwise
    // appear between descriptor elements and comment blocks. Note that if
    // detached comments are being printed, this will cause them to be merged
    // into the subsequent leading comments. Similarly, any element trailing
    // comments will be merged into the subsequent leading comments.
    Compact bool

    // If true, all references to messages, extensions, and enums (such as in
    // options, field types, and method request and response types) will be
    // fully-qualified. When left unset, the referenced elements will contain
    // only as much qualifier as is required.
    // For example, if a message is in the same package as the reference, the
    // simple name can be used. If a message shares some context with the
    // reference, only the unshared context needs to be included. For example:
    //  message Foo {
    //    message Bar {
    //      enum Baz {
    //        ZERO = 0;
    //        ONE = 1;
    //      }
    //    }
    //    // This field shares some context as the enum it references: they are
    //    // both inside of the namespace Foo:
    //    //    field is "Foo.my_baz"
    //    //     enum is "Foo.Bar.Baz"
    //    // So we only need to qualify the reference with the context that they
    //    // do NOT have in common:
    //    Bar.Baz my_baz = 1;
    //  }
    // When printing fully-qualified names, they will be preceded by a dot, to
    // avoid any ambiguity that they might be relative vs. fully-qualified.
    ForceFullyQualifiedNames bool

Printer knows how to format file descriptors as proto source code. Its fields provide some control over how the resulting source file is constructed and formatted.

func (*Printer) PrintProtoFile Uses

func (p *Printer) PrintProtoFile(fd *desc.FileDescriptor, out io.Writer) error

PrintProtoFile prints the given single file descriptor to the given writer.

func (*Printer) PrintProtoFiles Uses

func (p *Printer) PrintProtoFiles(fds []*desc.FileDescriptor, open func(name string) (io.WriteCloser, error)) error

PrintProtoFiles prints all of the given file descriptors. The given open function is given a file name and is responsible for creating the outputs and returning the corresponding writer.

func (*Printer) PrintProtoToString Uses

func (p *Printer) PrintProtoToString(dsc desc.Descriptor) (string, error)

PrintProto prints the given descriptor and returns the resulting string. This can be used to print proto files, but it can also be used to get the proto "source form" for any kind of descriptor, which can be a more user-friendly way to present descriptors that are intended for human consumption.

func (*Printer) PrintProtosToFileSystem Uses

func (p *Printer) PrintProtosToFileSystem(fds []*desc.FileDescriptor, rootDir string) error

PrintProtosToFileSystem prints all of the given file descriptors to files in the given directory. If file names in the given descriptors include path information, they will be relative to the given root.

Package protoprint imports 14 packages (graph) and is imported by 8 packages. Updated 2020-11-27. Refresh now. Tools for package owners.