protobug_compiler_protos 0.1.0

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml ADDED
@@ -0,0 +1,7 @@
1
+ ---
2
+ SHA256:
3
+ metadata.gz: 149e728b975c0009ad6728b1744a2563ce89ea2a8adfc791985c18bf5f1be173
4
+ data.tar.gz: a4a06ca94dbe3e6550fb979824d99e090372b1a783c2c7b7db857a1400b885ee
5
+ SHA512:
6
+ metadata.gz: 2fc738e303b580b748bd8ec993ef577c8d58daadee0584240ca814084ad56b52d798724d92102084f8d55919faa69ec2f2a8d338c5aa8577c8b4c953f0f8ba87
7
+ data.tar.gz: 01f87812685ede351914fe22c8572a5173feaf528f1d93c8c7dec61e46544e4bae1476a902c28fd363d8a15100f17e4cc610ce740afa93b9f79f0b639d836efb
@@ -0,0 +1,269 @@
1
+ # frozen_string_literal: true
2
+
3
+ # Code generated by protoc-gen-protobug. DO NOT EDIT.
4
+
5
+ # source: google/protobuf/compiler/plugin.proto
6
+ # syntax: proto2
7
+ # package: google.protobuf.compiler
8
+ # options:
9
+ # java_package: "com.google.protobuf.compiler"
10
+ # java_outer_classname: "PluginProtos"
11
+ # go_package: "google.golang.org/protobuf/types/pluginpb"
12
+ # csharp_namespace: "Google.Protobuf.Compiler"
13
+
14
+ # Protocol Buffers - Google's data interchange format
15
+ # Copyright 2008 Google Inc. All rights reserved.
16
+ #
17
+ # Use of this source code is governed by a BSD-style
18
+ # license that can be found in the LICENSE file or at
19
+ # https://developers.google.com/open-source/licenses/bsd
20
+
21
+ # Author: kenton@google.com (Kenton Varda)
22
+ #
23
+ # protoc (aka the Protocol Compiler) can be extended via plugins. A plugin is
24
+ # just a program that reads a CodeGeneratorRequest from stdin and writes a
25
+ # CodeGeneratorResponse to stdout.
26
+ #
27
+ # Plugins written using C++ can use google/protobuf/compiler/plugin.h instead
28
+ # of dealing with the raw protocol defined here.
29
+ #
30
+ # A plugin executable needs only to be placed somewhere in the path. The
31
+ # plugin should be named "protoc-gen-$NAME", and will then be used when the
32
+ # flag "--${NAME}_out" is passed to protoc.
33
+
34
+ require "protobug"
35
+
36
+ require "google/protobuf/descriptor_pb"
37
+
38
+ module Google
39
+ module Protobuf
40
+ module Compiler
41
+ # The version number of protocol compiler.
42
+ class Version
43
+ extend Protobug::Message
44
+
45
+ self.full_name = "google.protobuf.compiler.Version"
46
+
47
+ optional(1, "major", type: :int32)
48
+ optional(2, "minor", type: :int32)
49
+ optional(3, "patch", type: :int32)
50
+ # A suffix for alpha, beta or rc release, e.g., "alpha-1", "rc2". It should
51
+ # be empty for mainline stable releases.
52
+ optional(4, "suffix", type: :string)
53
+ end
54
+
55
+ # An encoded CodeGeneratorRequest is written to the plugin's stdin.
56
+ class CodeGeneratorRequest
57
+ extend Protobug::Message
58
+
59
+ self.full_name = "google.protobuf.compiler.CodeGeneratorRequest"
60
+
61
+ # The .proto files that were explicitly listed on the command-line. The
62
+ # code generator should generate code only for these files. Each file's
63
+ # descriptor will be included in proto_file, below.
64
+ repeated(
65
+ 1,
66
+ "file_to_generate",
67
+ type: :string,
68
+ json_name: "fileToGenerate"
69
+ )
70
+ # The generator parameter passed on the command-line.
71
+ optional(2, "parameter", type: :string)
72
+ # FileDescriptorProtos for all files in files_to_generate and everything
73
+ # they import. The files will appear in topological order, so each file
74
+ # appears before any file that imports it.
75
+ #
76
+ # Note: the files listed in files_to_generate will include runtime-retention
77
+ # options only, but all other files will include source-retention options.
78
+ # The source_file_descriptors field below is available in case you need
79
+ # source-retention options for files_to_generate.
80
+ #
81
+ # protoc guarantees that all proto_files will be written after
82
+ # the fields above, even though this is not technically guaranteed by the
83
+ # protobuf wire format. This theoretically could allow a plugin to stream
84
+ # in the FileDescriptorProtos and handle them one by one rather than read
85
+ # the entire set into memory at once. However, as of this writing, this
86
+ # is not similarly optimized on protoc's end -- it will store all fields in
87
+ # memory at once before sending them to the plugin.
88
+ #
89
+ # Type names of fields and extensions in the FileDescriptorProto are always
90
+ # fully qualified.
91
+ repeated(
92
+ 15,
93
+ "proto_file",
94
+ type: :message,
95
+ message_type: "google.protobuf.FileDescriptorProto",
96
+ json_name: "protoFile"
97
+ )
98
+ # File descriptors with all options, including source-retention options.
99
+ # These descriptors are only provided for the files listed in
100
+ # files_to_generate.
101
+ repeated(
102
+ 17,
103
+ "source_file_descriptors",
104
+ type: :message,
105
+ message_type: "google.protobuf.FileDescriptorProto",
106
+ json_name: "sourceFileDescriptors"
107
+ )
108
+ # The version number of protocol compiler.
109
+ optional(
110
+ 3,
111
+ "compiler_version",
112
+ type: :message,
113
+ message_type: "google.protobuf.compiler.Version",
114
+ json_name: "compilerVersion"
115
+ )
116
+ end
117
+
118
+ # The plugin writes an encoded CodeGeneratorResponse to stdout.
119
+ class CodeGeneratorResponse
120
+ extend Protobug::Message
121
+
122
+ self.full_name = "google.protobuf.compiler.CodeGeneratorResponse"
123
+
124
+ # Error message. If non-empty, code generation failed. The plugin process
125
+ # should exit with status code zero even if it reports an error in this way.
126
+ #
127
+ # This should be used to indicate errors in .proto files which prevent the
128
+ # code generator from generating correct code. Errors which indicate a
129
+ # problem in protoc itself -- such as the input CodeGeneratorRequest being
130
+ # unparseable -- should be reported by writing a message to stderr and
131
+ # exiting with a non-zero status code.
132
+ optional(1, "error", type: :string)
133
+ # A bitmask of supported features that the code generator supports.
134
+ # This is a bitwise "or" of values from the Feature enum.
135
+ optional(
136
+ 2,
137
+ "supported_features",
138
+ type: :uint64,
139
+ json_name: "supportedFeatures"
140
+ )
141
+ # Sync with code_generator.h.
142
+ class Feature
143
+ extend Protobug::Enum
144
+
145
+ self.full_name = "google.protobuf.compiler.CodeGeneratorResponse.Feature"
146
+
147
+ FEATURE_NONE = new("FEATURE_NONE", 0).freeze
148
+ FEATURE_PROTO3_OPTIONAL = new("FEATURE_PROTO3_OPTIONAL", 1).freeze
149
+ FEATURE_SUPPORTS_EDITIONS = new("FEATURE_SUPPORTS_EDITIONS", 2).freeze
150
+ end
151
+
152
+ # The minimum edition this plugin supports. This will be treated as an
153
+ # Edition enum, but we want to allow unknown values. It should be specified
154
+ # according the edition enum value, *not* the edition number. Only takes
155
+ # effect for plugins that have FEATURE_SUPPORTS_EDITIONS set.
156
+ optional(
157
+ 3,
158
+ "minimum_edition",
159
+ type: :int32,
160
+ json_name: "minimumEdition"
161
+ )
162
+ # The maximum edition this plugin supports. This will be treated as an
163
+ # Edition enum, but we want to allow unknown values. It should be specified
164
+ # according the edition enum value, *not* the edition number. Only takes
165
+ # effect for plugins that have FEATURE_SUPPORTS_EDITIONS set.
166
+ optional(
167
+ 4,
168
+ "maximum_edition",
169
+ type: :int32,
170
+ json_name: "maximumEdition"
171
+ )
172
+ # Represents a single generated file.
173
+ class File
174
+ extend Protobug::Message
175
+
176
+ self.full_name = "google.protobuf.compiler.CodeGeneratorResponse.File"
177
+
178
+ # The file name, relative to the output directory. The name must not
179
+ # contain "." or ".." components and must be relative, not be absolute (so,
180
+ # the file cannot lie outside the output directory). "/" must be used as
181
+ # the path separator, not "\".
182
+ #
183
+ # If the name is omitted, the content will be appended to the previous
184
+ # file. This allows the generator to break large files into small chunks,
185
+ # and allows the generated text to be streamed back to protoc so that large
186
+ # files need not reside completely in memory at one time. Note that as of
187
+ # this writing protoc does not optimize for this -- it will read the entire
188
+ # CodeGeneratorResponse before writing files to disk.
189
+ optional(1, "name", type: :string)
190
+ # If non-empty, indicates that the named file should already exist, and the
191
+ # content here is to be inserted into that file at a defined insertion
192
+ # point. This feature allows a code generator to extend the output
193
+ # produced by another code generator. The original generator may provide
194
+ # insertion points by placing special annotations in the file that look
195
+ # like:
196
+ # @@protoc_insertion_point(NAME)
197
+ # The annotation can have arbitrary text before and after it on the line,
198
+ # which allows it to be placed in a comment. NAME should be replaced with
199
+ # an identifier naming the point -- this is what other generators will use
200
+ # as the insertion_point. Code inserted at this point will be placed
201
+ # immediately above the line containing the insertion point (thus multiple
202
+ # insertions to the same point will come out in the order they were added).
203
+ # The double-@ is intended to make it unlikely that the generated code
204
+ # could contain things that look like insertion points by accident.
205
+ #
206
+ # For example, the C++ code generator places the following line in the
207
+ # .pb.h files that it generates:
208
+ # // @@protoc_insertion_point(namespace_scope)
209
+ # This line appears within the scope of the file's package namespace, but
210
+ # outside of any particular class. Another plugin can then specify the
211
+ # insertion_point "namespace_scope" to generate additional classes or
212
+ # other declarations that should be placed in this scope.
213
+ #
214
+ # Note that if the line containing the insertion point begins with
215
+ # whitespace, the same whitespace will be added to every line of the
216
+ # inserted text. This is useful for languages like Python, where
217
+ # indentation matters. In these languages, the insertion point comment
218
+ # should be indented the same amount as any inserted code will need to be
219
+ # in order to work correctly in that context.
220
+ #
221
+ # The code generator that generates the initial file and the one which
222
+ # inserts into it must both run as part of a single invocation of protoc.
223
+ # Code generators are executed in the order in which they appear on the
224
+ # command line.
225
+ #
226
+ # If |insertion_point| is present, |name| must also be present.
227
+ optional(
228
+ 2,
229
+ "insertion_point",
230
+ type: :string,
231
+ json_name: "insertionPoint"
232
+ )
233
+ # The file contents.
234
+ optional(15, "content", type: :string)
235
+ # Information describing the file content being inserted. If an insertion
236
+ # point is used, this information will be appropriately offset and inserted
237
+ # into the code generation metadata for the generated files.
238
+ optional(
239
+ 16,
240
+ "generated_code_info",
241
+ type: :message,
242
+ message_type: "google.protobuf.GeneratedCodeInfo",
243
+ json_name: "generatedCodeInfo"
244
+ )
245
+ end
246
+
247
+ repeated(
248
+ 15,
249
+ "file",
250
+ type: :message,
251
+ message_type: "google.protobuf.compiler.CodeGeneratorResponse.File"
252
+ )
253
+ end
254
+
255
+ def self.register_plugin_protos(registry)
256
+ Google::Protobuf.register_descriptor_protos(registry)
257
+ registry.register(Google::Protobuf::Compiler::Version)
258
+ registry.register(Google::Protobuf::Compiler::CodeGeneratorRequest)
259
+ registry.register(Google::Protobuf::Compiler::CodeGeneratorResponse)
260
+ registry.register(
261
+ Google::Protobuf::Compiler::CodeGeneratorResponse::Feature
262
+ )
263
+ registry.register(
264
+ Google::Protobuf::Compiler::CodeGeneratorResponse::File
265
+ )
266
+ end
267
+ end
268
+ end
269
+ end
@@ -0,0 +1,5 @@
1
+ # frozen_string_literal: true
2
+
3
+ require "protobug"
4
+
5
+ require_relative "google/protobuf/compiler/plugin_pb"
metadata ADDED
@@ -0,0 +1,75 @@
1
+ --- !ruby/object:Gem::Specification
2
+ name: protobug_compiler_protos
3
+ version: !ruby/object:Gem::Version
4
+ version: 0.1.0
5
+ platform: ruby
6
+ authors:
7
+ - Samuel Giddins
8
+ autorequire:
9
+ bindir: bin
10
+ cert_chain: []
11
+ date: 2024-04-25 00:00:00.000000000 Z
12
+ dependencies:
13
+ - !ruby/object:Gem::Dependency
14
+ name: protobug
15
+ requirement: !ruby/object:Gem::Requirement
16
+ requirements:
17
+ - - '='
18
+ - !ruby/object:Gem::Version
19
+ version: 0.1.0
20
+ type: :runtime
21
+ prerelease: false
22
+ version_requirements: !ruby/object:Gem::Requirement
23
+ requirements:
24
+ - - '='
25
+ - !ruby/object:Gem::Version
26
+ version: 0.1.0
27
+ - !ruby/object:Gem::Dependency
28
+ name: protobug_well_known_protos
29
+ requirement: !ruby/object:Gem::Requirement
30
+ requirements:
31
+ - - '='
32
+ - !ruby/object:Gem::Version
33
+ version: 0.1.0
34
+ type: :runtime
35
+ prerelease: false
36
+ version_requirements: !ruby/object:Gem::Requirement
37
+ requirements:
38
+ - - '='
39
+ - !ruby/object:Gem::Version
40
+ version: 0.1.0
41
+ description:
42
+ email:
43
+ - segiddins@segiddins.me
44
+ executables: []
45
+ extensions: []
46
+ extra_rdoc_files: []
47
+ files:
48
+ - lib/google/protobuf/compiler/plugin_pb.rb
49
+ - lib/protobug_compiler_protos.rb
50
+ homepage: https://github.com/segiddins/protobug/blob/v0.1.0/gen/protobug_compiler_protos
51
+ licenses:
52
+ - Unlicense
53
+ metadata:
54
+ rubygems_mfa_required: 'true'
55
+ post_install_message:
56
+ rdoc_options: []
57
+ require_paths:
58
+ - lib
59
+ required_ruby_version: !ruby/object:Gem::Requirement
60
+ requirements:
61
+ - - ">="
62
+ - !ruby/object:Gem::Version
63
+ version: 3.0.0
64
+ required_rubygems_version: !ruby/object:Gem::Requirement
65
+ requirements:
66
+ - - ">="
67
+ - !ruby/object:Gem::Version
68
+ version: '0'
69
+ requirements: []
70
+ rubygems_version: 3.5.9
71
+ signing_key:
72
+ specification_version: 4
73
+ summary: Compiled protos for protobug from https://github.com/protocolbuffers/protobuf
74
+ (compiler_protos)
75
+ test_files: []