protostar 0.1.0.beta1

data/lib/protostar/google/protobuf/api_pb.rb

@@ -0,0 +1,199 @@
+# frozen_string_literal: true
+
+# Generated by protostar from google/protobuf/api.proto. Do not edit.
+
+require "protostar"
+require "protostar/google/protobuf/source_context_pb"
+require "protostar/google/protobuf/type_pb"
+
+Protostar::DSL.file(
+  "google/protobuf/api.proto",
+  package: "google.protobuf",
+  syntax: :proto3,
+  dependencies: ["google/protobuf/source_context.proto", "google/protobuf/type.proto"],
+  java_package: "com.google.protobuf",
+  java_outer_classname: "ApiProto",
+  java_multiple_files: true,
+  objc_class_prefix: "GPB",
+  csharp_namespace: "Google.Protobuf.WellKnownTypes",
+  go_package: "google.golang.org/protobuf/types/known/apipb"
+) do |f|
+  # Api is a light-weight descriptor for an API Interface.
+  #
+  # Interfaces are also described as "protocol buffer services" in some contexts,
+  # such as by the "service" keyword in a .proto file, but they are different
+  # from API Services, which represent a concrete implementation of an interface
+  # as opposed to simply a description of methods and bindings. They are also
+  # sometimes simply referred to as "APIs" in other contexts, such as the name of
+  # this message itself. See https://cloud.google.com/apis/design/glossary for
+  # detailed terminology.
+  #
+  # New usages of this message as an alternative to ServiceDescriptorProto are
+  # strongly discouraged. This message does not reliability preserve all
+  # information necessary to model the schema and preserve semantics. Instead
+  # make use of FileDescriptorSet which preserves the necessary information.
+  f.message "Api" do |m|
+    # The fully qualified name of this interface, including package name
+    # followed by the interface's simple name.
+    m.field :name, 1, :string
+    # The methods of this interface, in unspecified order.
+    m.field :methods, 2, :message, ".google.protobuf.Method", label: :repeated
+    # Any metadata attached to the interface.
+    m.field :options, 3, :message, ".google.protobuf.Option", label: :repeated
+    # A version string for this interface. If specified, must have the form
+    # `major-version.minor-version`, as in `1.10`. If the minor version is
+    # omitted, it defaults to zero. If the entire version field is empty, the
+    # major version is derived from the package name, as outlined below. If the
+    # field is not empty, the version in the package name will be verified to be
+    # consistent with what is provided here.
+    #
+    # The versioning schema uses [semantic
+    # versioning](http://semver.org) where the major version number
+    # indicates a breaking change and the minor version an additive,
+    # non-breaking change. Both version numbers are signals to users
+    # what to expect from different versions, and should be carefully
+    # chosen based on the product plan.
+    #
+    # The major version is also reflected in the package name of the
+    # interface, which must end in `v<major-version>`, as in
+    # `google.feature.v1`. For major versions 0 and 1, the suffix can
+    # be omitted. Zero major versions must only be used for
+    # experimental, non-GA interfaces.
+    #
+    m.field :version, 4, :string
+    # Source context for the protocol buffer service represented by this
+    # message.
+    m.field :source_context, 5, :message, ".google.protobuf.SourceContext"
+    # Included interfaces. See [Mixin][].
+    m.field :mixins, 6, :message, ".google.protobuf.Mixin", label: :repeated
+    # The source syntax of the service.
+    m.field :syntax, 7, :enum, ".google.protobuf.Syntax"
+    # The source edition string, only valid when syntax is SYNTAX_EDITIONS.
+    m.field :edition, 8, :string
+  end
+  # Method represents a method of an API interface.
+  #
+  # New usages of this message as an alternative to MethodDescriptorProto are
+  # strongly discouraged. This message does not reliability preserve all
+  # information necessary to model the schema and preserve semantics. Instead
+  # make use of FileDescriptorSet which preserves the necessary information.
+  f.message "Method" do |m|
+    # The simple name of this method.
+    m.field :name, 1, :string
+    # A URL of the input message type.
+    m.field :request_type_url, 2, :string
+    # If true, the request is streamed.
+    m.field :request_streaming, 3, :bool
+    # The URL of the output message type.
+    m.field :response_type_url, 4, :string
+    # If true, the response is streamed.
+    m.field :response_streaming, 5, :bool
+    # Any metadata attached to the method.
+    m.field :options, 6, :message, ".google.protobuf.Option", label: :repeated
+    # The source syntax of this method.
+    #
+    # This field should be ignored, instead the syntax should be inherited from
+    # Api. This is similar to Field and EnumValue.
+    m.field :syntax, 7, :enum, ".google.protobuf.Syntax", deprecated: true
+    # The source edition string, only valid when syntax is SYNTAX_EDITIONS.
+    #
+    # This field should be ignored, instead the edition should be inherited from
+    # Api. This is similar to Field and EnumValue.
+    m.field :edition, 8, :string, deprecated: true
+  end
+  # Declares an API Interface to be included in this interface. The including
+  # interface must redeclare all the methods from the included interface, but
+  # documentation and options are inherited as follows:
+  #
+  # - If after comment and whitespace stripping, the documentation
+  #   string of the redeclared method is empty, it will be inherited
+  #   from the original method.
+  #
+  # - Each annotation belonging to the service config (http,
+  #   visibility) which is not set in the redeclared method will be
+  #   inherited.
+  #
+  # - If an http annotation is inherited, the path pattern will be
+  #   modified as follows. Any version prefix will be replaced by the
+  #   version of the including interface plus the [root][] path if
+  #   specified.
+  #
+  # Example of a simple mixin:
+  #
+  #     package google.acl.v1;
+  #     service AccessControl {
+  #       // Get the underlying ACL object.
+  #       rpc GetAcl(GetAclRequest) returns (Acl) {
+  #         option (google.api.http).get = "/v1/{resource=**}:getAcl";
+  #       }
+  #     }
+  #
+  #     package google.storage.v2;
+  #     service Storage {
+  #       rpc GetAcl(GetAclRequest) returns (Acl);
+  #
+  #       // Get a data record.
+  #       rpc GetData(GetDataRequest) returns (Data) {
+  #         option (google.api.http).get = "/v2/{resource=**}";
+  #       }
+  #     }
+  #
+  # Example of a mixin configuration:
+  #
+  #     apis:
+  #     - name: google.storage.v2.Storage
+  #       mixins:
+  #       - name: google.acl.v1.AccessControl
+  #
+  # The mixin construct implies that all methods in `AccessControl` are
+  # also declared with same name and request/response types in
+  # `Storage`. A documentation generator or annotation processor will
+  # see the effective `Storage.GetAcl` method after inheriting
+  # documentation and annotations as follows:
+  #
+  #     service Storage {
+  #       // Get the underlying ACL object.
+  #       rpc GetAcl(GetAclRequest) returns (Acl) {
+  #         option (google.api.http).get = "/v2/{resource=**}:getAcl";
+  #       }
+  #       ...
+  #     }
+  #
+  # Note how the version in the path pattern changed from `v1` to `v2`.
+  #
+  # If the `root` field in the mixin is specified, it should be a
+  # relative path under which inherited HTTP paths are placed. Example:
+  #
+  #     apis:
+  #     - name: google.storage.v2.Storage
+  #       mixins:
+  #       - name: google.acl.v1.AccessControl
+  #         root: acls
+  #
+  # This implies the following inherited HTTP annotation:
+  #
+  #     service Storage {
+  #       // Get the underlying ACL object.
+  #       rpc GetAcl(GetAclRequest) returns (Acl) {
+  #         option (google.api.http).get = "/v2/acls/{resource=**}:getAcl";
+  #       }
+  #       ...
+  #     }
+  f.message "Mixin" do |m|
+    # The fully qualified name of the interface which is included.
+    m.field :name, 1, :string
+    # If non-empty specifies a path under which inherited HTTP paths
+    # are rooted.
+    m.field :root, 2, :string
+  end
+end
+
+module Protostar
+  module Google
+    module Protobuf
+      Api = Protostar::DSL.message("google.protobuf.Api")
+      Method = Protostar::DSL.message("google.protobuf.Method")
+      Mixin = Protostar::DSL.message("google.protobuf.Mixin")
+    end
+  end
+end

data/lib/protostar/google/protobuf/compiler/plugin_pb.rb

@@ -0,0 +1,168 @@
+# frozen_string_literal: true
+
+# Generated by protostar from google/protobuf/compiler/plugin.proto. Do not edit.
+
+require "protostar"
+require "protostar/google/protobuf/descriptor_pb"
+
+Protostar::DSL.file(
+  "google/protobuf/compiler/plugin.proto",
+  package: "google.protobuf.compiler",
+  dependencies: ["google/protobuf/descriptor.proto"],
+  java_package: "com.google.protobuf.compiler",
+  java_outer_classname: "PluginProtos",
+  csharp_namespace: "Google.Protobuf.Compiler",
+  go_package: "google.golang.org/protobuf/types/pluginpb"
+) do |f|
+  # The version number of protocol compiler.
+  f.message "Version" do |m|
+    m.field :major, 1, :int32
+    m.field :minor, 2, :int32
+    m.field :patch, 3, :int32
+    # A suffix for alpha, beta or rc release, e.g., "alpha-1", "rc2". It should
+    # be empty for mainline stable releases.
+    m.field :suffix, 4, :string
+  end
+  # An encoded CodeGeneratorRequest is written to the plugin's stdin.
+  f.message "CodeGeneratorRequest" do |m|
+    # The .proto files that were explicitly listed on the command-line.  The
+    # code generator should generate code only for these files.  Each file's
+    # descriptor will be included in proto_file, below.
+    m.field :file_to_generate, 1, :string, label: :repeated
+    # The generator parameter passed on the command-line.
+    m.field :parameter, 2, :string
+    # FileDescriptorProtos for all files in files_to_generate and everything
+    # they import.  The files will appear in topological order, so each file
+    # appears before any file that imports it.
+    #
+    # Note: the files listed in files_to_generate will include runtime-retention
+    # options only, but all other files will include source-retention options.
+    # The source_file_descriptors field below is available in case you need
+    # source-retention options for files_to_generate.
+    #
+    # protoc guarantees that all proto_files will be written after
+    # the fields above, even though this is not technically guaranteed by the
+    # protobuf wire format.  This theoretically could allow a plugin to stream
+    # in the FileDescriptorProtos and handle them one by one rather than read
+    # the entire set into memory at once.  However, as of this writing, this
+    # is not similarly optimized on protoc's end -- it will store all fields in
+    # memory at once before sending them to the plugin.
+    #
+    # Type names of fields and extensions in the FileDescriptorProto are always
+    # fully qualified.
+    m.field :proto_file, 15, :message, ".google.protobuf.FileDescriptorProto", label: :repeated
+    # File descriptors with all options, including source-retention options.
+    # These descriptors are only provided for the files listed in
+    # files_to_generate.
+    m.field :source_file_descriptors, 17, :message, ".google.protobuf.FileDescriptorProto",
+      label: :repeated
+    # The version number of protocol compiler.
+    m.field :compiler_version, 3, :message, ".google.protobuf.compiler.Version"
+  end
+  # The plugin writes an encoded CodeGeneratorResponse to stdout.
+  f.message "CodeGeneratorResponse" do |m|
+    # Error message.  If non-empty, code generation failed.  The plugin process
+    # should exit with status code zero even if it reports an error in this way.
+    #
+    # This should be used to indicate errors in .proto files which prevent the
+    # code generator from generating correct code.  Errors which indicate a
+    # problem in protoc itself -- such as the input CodeGeneratorRequest being
+    # unparseable -- should be reported by writing a message to stderr and
+    # exiting with a non-zero status code.
+    m.field :error, 1, :string
+    # A bitmask of supported features that the code generator supports.
+    # This is a bitwise "or" of values from the Feature enum.
+    m.field :supported_features, 2, :uint64
+    # The minimum edition this plugin supports.  This will be treated as an
+    # Edition enum, but we want to allow unknown values.  It should be specified
+    # according the edition enum value, *not* the edition number.  Only takes
+    # effect for plugins that have FEATURE_SUPPORTS_EDITIONS set.
+    m.field :minimum_edition, 3, :int32
+    # The maximum edition this plugin supports.  This will be treated as an
+    # Edition enum, but we want to allow unknown values.  It should be specified
+    # according the edition enum value, *not* the edition number.  Only takes
+    # effect for plugins that have FEATURE_SUPPORTS_EDITIONS set.
+    m.field :maximum_edition, 4, :int32
+    m.field :file, 15, :message, ".google.protobuf.compiler.CodeGeneratorResponse.File",
+      label: :repeated
+    # Represents a single generated file.
+    m.message "File" do |m|
+      # 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.
+      m.field :name, 1, :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.
+      m.field :insertion_point, 2, :string
+      # The file contents.
+      m.field :content, 15, :string
+      # 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.
+      m.field :generated_code_info, 16, :message, ".google.protobuf.GeneratedCodeInfo"
+    end
+    # Sync with code_generator.h.
+    m.enum "Feature" do |e|
+      e.value :FEATURE_NONE, 0
+      e.value :FEATURE_PROTO3_OPTIONAL, 1
+      e.value :FEATURE_SUPPORTS_EDITIONS, 2
+    end
+  end
+end
+
+module Protostar
+  module Google
+    module Protobuf
+      module Compiler
+        Version = Protostar::DSL.message("google.protobuf.compiler.Version")
+        CodeGeneratorRequest = Protostar::DSL.message("google.protobuf.compiler.CodeGeneratorRequest")
+        CodeGeneratorResponse = Protostar::DSL.message("google.protobuf.compiler.CodeGeneratorResponse")
+        CodeGeneratorResponse::File = Protostar::DSL.message("google.protobuf.compiler.CodeGeneratorResponse.File")
+        CodeGeneratorResponse::Feature = Protostar::DSL.enum("google.protobuf.compiler.CodeGeneratorResponse.Feature")
+      end
+    end
+  end
+end