Skip to content

Milliseconds are read incorrectly from time and date time literals #1702

@antvaset

Description

@antvaset

Currently, @T10:30:15.1 is interpreted as a Time object with milliseconds set to 1 and not 100. Same applies to date time literals like @2014-02-12T10:30:15.1.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    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