Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

wrong timestamp parser when xAxis type is 'time'

See original GitHub issue

Version

4.8.0

Steps to reproduce

following timestamp is around 2020-08-04 10:11:00

option = {
    xAxis: {
        data: [1596507060, 1596507160, 1596507260], // second
        type : 'time'
    },
    yAxis: {},
    series: [{
        type: 'line',
        data:[220, 182, 191]
    }]
};

option = {
    xAxis: {
        data: [1596507060000, 1596507160000, 1596507260000], // milliseconds
        type : 'time'
    },
    yAxis: {},
    series: [{
        type: 'line',
        data:[220, 182, 191]
    }]
};

option = {
    xAxis: {
        data: [1596507060.000, 1596507160.000, 1596507260.000], // second with decimal
        type : 'time'
    },
    yAxis: {},
    series: [{
        type: 'line',
        data:[220, 182, 191]
    }]
};

What is expected?

According to https://echarts.apache.org/en/option.html#series-line.data, timestamp can be used as axis value when type is ‘time’.

right parsing of x axis timestamp, timestamp is around 2020-08-04 10:11:00

What is actually happening?

timestamp displays 08:00:00
wrong xaxis interval
wrong y axis value trending

Issue Analytics

State:
Created 3 years ago
Comments:5 (2 by maintainers)

Top GitHub Comments

12reactions

plainheartcommented, Aug 4, 2020

It may be not a bug but an incorrect usage. xAxis.data is just for the type of category. If the type is time, it can’t be specified.

Category data, available in type: ‘category’ axis.

When the type of xAxis is time, the time should be specified as a dimension in the series.data.

Example:

option = {
    xAxis: {
        type : 'time'
    },
    yAxis: {},
    series: [{
        type: 'line',
        data:[
            [1596507060000, 220],
            [1596507160000, 182],
            [1596507260000, 191]
        ]
    }]
};

0reactions

plainheartcommented, Aug 4, 2020

@wlbksy I’m afraid we can’t. For a numerical timestamp, ECharts will parse it to a Date object by new Date(timestamp).