You've already forked dart-core-sdk
Latest generation
This commit is contained in:
@@ -52,15 +52,9 @@ class Version extends $pb.GeneratedMessage {
|
||||
..hasRequiredFields = false
|
||||
;
|
||||
|
||||
@$core.Deprecated(
|
||||
'Using this can add significant overhead to your binary. '
|
||||
'Use [GeneratedMessageGenericExtensions.deepCopy] instead. '
|
||||
'Will be removed in next major version')
|
||||
@$core.Deprecated('See https://github.com/google/protobuf.dart/issues/998.')
|
||||
Version clone() => Version()..mergeFromMessage(this);
|
||||
@$core.Deprecated(
|
||||
'Using this can add significant overhead to your binary. '
|
||||
'Use [GeneratedMessageGenericExtensions.rebuild] instead. '
|
||||
'Will be removed in next major version')
|
||||
@$core.Deprecated('See https://github.com/google/protobuf.dart/issues/998.')
|
||||
Version copyWith(void Function(Version) updates) => super.copyWith((message) => updates(message as Version)) as Version;
|
||||
|
||||
$pb.BuilderInfo get info_ => _i;
|
||||
@@ -146,15 +140,9 @@ class CodeGeneratorRequest extends $pb.GeneratedMessage {
|
||||
..pc<$89.FileDescriptorProto>(15, _omitFieldNames ? '' : 'protoFile', $pb.PbFieldType.PM, subBuilder: $89.FileDescriptorProto.create)
|
||||
;
|
||||
|
||||
@$core.Deprecated(
|
||||
'Using this can add significant overhead to your binary. '
|
||||
'Use [GeneratedMessageGenericExtensions.deepCopy] instead. '
|
||||
'Will be removed in next major version')
|
||||
@$core.Deprecated('See https://github.com/google/protobuf.dart/issues/998.')
|
||||
CodeGeneratorRequest clone() => CodeGeneratorRequest()..mergeFromMessage(this);
|
||||
@$core.Deprecated(
|
||||
'Using this can add significant overhead to your binary. '
|
||||
'Use [GeneratedMessageGenericExtensions.rebuild] instead. '
|
||||
'Will be removed in next major version')
|
||||
@$core.Deprecated('See https://github.com/google/protobuf.dart/issues/998.')
|
||||
CodeGeneratorRequest copyWith(void Function(CodeGeneratorRequest) updates) => super.copyWith((message) => updates(message as CodeGeneratorRequest)) as CodeGeneratorRequest;
|
||||
|
||||
$pb.BuilderInfo get info_ => _i;
|
||||
@@ -195,20 +183,20 @@ class CodeGeneratorRequest extends $pb.GeneratedMessage {
|
||||
@$pb.TagNumber(3)
|
||||
Version ensureCompilerVersion() => $_ensure(2);
|
||||
|
||||
/// 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.
|
||||
/// 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.
|
||||
///
|
||||
/// 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.
|
||||
/// 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.
|
||||
/// Type names of fields and extensions in the FileDescriptorProto are always
|
||||
/// fully qualified.
|
||||
@$pb.TagNumber(15)
|
||||
$pb.PbList<$89.FileDescriptorProto> get protoFile => $_getList(3);
|
||||
}
|
||||
@@ -243,15 +231,9 @@ class CodeGeneratorResponse_File extends $pb.GeneratedMessage {
|
||||
..hasRequiredFields = false
|
||||
;
|
||||
|
||||
@$core.Deprecated(
|
||||
'Using this can add significant overhead to your binary. '
|
||||
'Use [GeneratedMessageGenericExtensions.deepCopy] instead. '
|
||||
'Will be removed in next major version')
|
||||
@$core.Deprecated('See https://github.com/google/protobuf.dart/issues/998.')
|
||||
CodeGeneratorResponse_File clone() => CodeGeneratorResponse_File()..mergeFromMessage(this);
|
||||
@$core.Deprecated(
|
||||
'Using this can add significant overhead to your binary. '
|
||||
'Use [GeneratedMessageGenericExtensions.rebuild] instead. '
|
||||
'Will be removed in next major version')
|
||||
@$core.Deprecated('See https://github.com/google/protobuf.dart/issues/998.')
|
||||
CodeGeneratorResponse_File copyWith(void Function(CodeGeneratorResponse_File) updates) => super.copyWith((message) => updates(message as CodeGeneratorResponse_File)) as CodeGeneratorResponse_File;
|
||||
|
||||
$pb.BuilderInfo get info_ => _i;
|
||||
@@ -264,17 +246,17 @@ class CodeGeneratorResponse_File extends $pb.GeneratedMessage {
|
||||
static CodeGeneratorResponse_File getDefault() => _defaultInstance ??= $pb.GeneratedMessage.$_defaultFor<CodeGeneratorResponse_File>(create);
|
||||
static CodeGeneratorResponse_File? _defaultInstance;
|
||||
|
||||
/// 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 "\".
|
||||
/// 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.
|
||||
/// 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.
|
||||
@$pb.TagNumber(1)
|
||||
$core.String get name => $_getSZ(0);
|
||||
@$pb.TagNumber(1)
|
||||
@@ -284,43 +266,43 @@ class CodeGeneratorResponse_File extends $pb.GeneratedMessage {
|
||||
@$pb.TagNumber(1)
|
||||
void clearName() => $_clearField(1);
|
||||
|
||||
/// 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.
|
||||
/// 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.
|
||||
/// 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.
|
||||
/// 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.
|
||||
/// 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.
|
||||
/// If |insertion_point| is present, |name| must also be present.
|
||||
@$pb.TagNumber(2)
|
||||
$core.String get insertionPoint => $_getSZ(1);
|
||||
@$pb.TagNumber(2)
|
||||
@@ -366,15 +348,9 @@ class CodeGeneratorResponse extends $pb.GeneratedMessage {
|
||||
..hasRequiredFields = false
|
||||
;
|
||||
|
||||
@$core.Deprecated(
|
||||
'Using this can add significant overhead to your binary. '
|
||||
'Use [GeneratedMessageGenericExtensions.deepCopy] instead. '
|
||||
'Will be removed in next major version')
|
||||
@$core.Deprecated('See https://github.com/google/protobuf.dart/issues/998.')
|
||||
CodeGeneratorResponse clone() => CodeGeneratorResponse()..mergeFromMessage(this);
|
||||
@$core.Deprecated(
|
||||
'Using this can add significant overhead to your binary. '
|
||||
'Use [GeneratedMessageGenericExtensions.rebuild] instead. '
|
||||
'Will be removed in next major version')
|
||||
@$core.Deprecated('See https://github.com/google/protobuf.dart/issues/998.')
|
||||
CodeGeneratorResponse copyWith(void Function(CodeGeneratorResponse) updates) => super.copyWith((message) => updates(message as CodeGeneratorResponse)) as CodeGeneratorResponse;
|
||||
|
||||
$pb.BuilderInfo get info_ => _i;
|
||||
@@ -387,14 +363,14 @@ class CodeGeneratorResponse extends $pb.GeneratedMessage {
|
||||
static CodeGeneratorResponse getDefault() => _defaultInstance ??= $pb.GeneratedMessage.$_defaultFor<CodeGeneratorResponse>(create);
|
||||
static CodeGeneratorResponse? _defaultInstance;
|
||||
|
||||
/// 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.
|
||||
/// 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.
|
||||
/// 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.
|
||||
@$pb.TagNumber(1)
|
||||
$core.String get error => $_getSZ(0);
|
||||
@$pb.TagNumber(1)
|
||||
|
||||
Reference in New Issue
Block a user