reflex-platform/dart-core-sdk
0
Fork 0
Code Pull Requests Projects Releases Wiki Activity

Release 1.12.3

Browse Source
This commit is contained in:
ci core model
2026-02-05 08:59:17 +00:00
parent a92412ba65
commit 0a93573435
44 changed files with 272 additions and 3595 deletions
Download Patch File Download Diff File Expand all files Collapse all files

28
lib/google/protobuf/timestamp.pb.dart
View File

@@ -69,15 +69,8 @@ export 'package:protobuf/protobuf.dart' show GeneratedMessageGenericExtensions;
/// Timestamp timestamp = Timestamp.newBuilder().setSeconds(millis / 1000)
/// .setNanos((int) ((millis % 1000) * 1000000)).build();
///
/// Example 5: Compute Timestamp from Java `Instant.now()`.
///
/// Instant now = Instant.now();
///
/// Timestamp timestamp =
/// Timestamp.newBuilder().setSeconds(now.getEpochSecond())
/// .setNanos(now.getNano()).build();
///
/// Example 6: Compute Timestamp from current time in Python.
/// Example 5: Compute Timestamp from current time in Python.
///
/// timestamp = Timestamp()
/// timestamp.GetCurrentTime()
@@ -91,8 +84,8 @@ export 'package:protobuf/protobuf.dart' show GeneratedMessageGenericExtensions;
/// {hour}, {min}, and {sec} are zero-padded to two digits each. The fractional
/// seconds, which can go up to 9 digits (i.e. up to 1 nanosecond resolution),
/// are optional. The "Z" suffix indicates the timezone ("UTC"); the timezone
/// is required. A ProtoJSON serializer should always use UTC (as indicated by
/// "Z") when printing the Timestamp type and a ProtoJSON parser should be
/// is required. A proto3 JSON serializer should always use UTC (as indicated by
/// "Z") when printing the Timestamp type and a proto3 JSON parser should be
/// able to accept both UTC and other timezones (as indicated by an offset).
///
/// For example, "2017-01-15T01:30:15.01Z" encodes 15.01 seconds past
@@ -106,7 +99,7 @@ export 'package:protobuf/protobuf.dart' show GeneratedMessageGenericExtensions;
/// [`strftime`](https://docs.python.org/2/library/time.html#time.strftime) with
/// the time format spec '%Y-%m-%dT%H:%M:%S.%fZ'. Likewise, in Java, one can use
/// the Joda Time's [`ISODateTimeFormat.dateTime()`](
/// http://joda-time.sourceforge.net/apidocs/org/joda/time/format/ISODateTimeFormat.html#dateTime()
/// http://www.joda.org/joda-time/apidocs/org/joda/time/format/ISODateTimeFormat.html#dateTime%2D%2D
/// ) to obtain a formatter capable of generating timestamps in this format.
class Timestamp extends $pb.GeneratedMessage with $mixin.TimestampMixin {
factory Timestamp({
@@ -147,9 +140,9 @@ class Timestamp extends $pb.GeneratedMessage with $mixin.TimestampMixin {
static Timestamp getDefault() => _defaultInstance ??= $pb.GeneratedMessage.$_defaultFor<Timestamp>(create);
static Timestamp? _defaultInstance;
/// Represents seconds of UTC time since Unix epoch 1970-01-01T00:00:00Z. Must
/// be between -62135596800 and 253402300799 inclusive (which corresponds to
/// 0001-01-01T00:00:00Z to 9999-12-31T23:59:59Z).
/// Represents seconds of UTC time since Unix epoch
/// 1970-01-01T00:00:00Z. Must be from 0001-01-01T00:00:00Z to
/// 9999-12-31T23:59:59Z inclusive.
@$pb.TagNumber(1)
$fixnum.Int64 get seconds => $_getI64(0);
@$pb.TagNumber(1)
@@ -159,10 +152,9 @@ class Timestamp extends $pb.GeneratedMessage with $mixin.TimestampMixin {
@$pb.TagNumber(1)
void clearSeconds() => $_clearField(1);
/// Non-negative fractions of a second at nanosecond resolution. This field is
/// the nanosecond portion of the duration, not an alternative to seconds.
/// Negative second values with fractions must still have non-negative nanos
/// values that count forward in time. Must be between 0 and 999,999,999
/// Non-negative fractions of a second at nanosecond resolution. Negative
/// second values with fractions must still have non-negative nanos values
/// that count forward in time. Must be from 0 to 999,999,999
/// inclusive.
@$pb.TagNumber(2)
$core.int get nanos => $_getIZ(1);