Skip to content

timestamp values cannot be of type js-uint because they support a smaller range #1112

@whimboo

Description

@whimboo

Currently we define timestamp values as js-uint across all events that include that given field. And js-uint is defined as:

js-uint = 0..9007199254740991

But based on the ECMA specification under Time Values and Time Range the following is mentioned:

A time value supports a slightly smaller range of -8,640,000,000,000,000 to 8,640,000,000,000,000 milliseconds. This yields a supported time value range of exactly -100,000,000 days to 100,000,000 days relative to midnight at the beginning of 1 January 1970 UTC.

Based on that we should define a separate type for timestamp values limited to just 0..8640000000000000.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingcddl

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions