calendar的range设置小于1000，会导致同一个实例的setOption方法无法执行。

[bigfacewo]

Version

5.1.1

Reproduction link

https://echarts.apache.org/examples/zh/editor.html?c=calendar-heatmap

Steps to reproduce

1. 将案例中的calendar的range设置为"999"，这时console会报一个错误：TypeError: Cannot read property 'slice' of undefined。
2. 如果只是不支持时间小于1000也是能理解，但是这时候继续调用setOption会报错： Uncaught Error: setOption should not be called during main process.。
3. 猜测是第一步的错误导致setOption中变量IN_MAIN_PROCESS_KEY的状态没有正确更新，导致后续无法再次调用setOption。

What is expected?

希望canlendar部分代码报错不要影响setOption的正常使用。

What is actually happening?

canlendar部分代码报错导致setOption无法再次调用。

---

如果每次都销毁实例，然后再调用setOption，是可以正常使用的。

[echarts-bot]

Hi! We've received your issue and please be patient to get responded. 🎉
The average response time is expected to be within one day for weekdays.

In the meanwhile, please make sure that it contains a minimum reproducible demo and necessary images to illustrate. Otherwise, our committers will ask you to do so.

A minimum reproducible demo should contain as little data and components as possible but can still illustrate your problem. This is the best way for us to reproduce it and solve the problem faster.

You may also check out the API and chart option to get the answer.

If you don't get helped for a long time (over a week) or have an urgent question to ask, you may also send an email to dev@echarts.apache.org. Please attach the issue link if it's a technical question.

If you are interested in the project, you may also subscribe our mailing list.

Have a nice day! 🍵

[echarts-bot]

@bigfacewo It seems you are not using English, I've helped translate the content automatically. To make your issue understood by more people, we'd like to suggest using English next time. 🤗

TRANSLATED

TITLE

If the range setting of calendar is less than 1000, the setOption method of the same instance cannot be executed.

BODY

Version

5.1.1

Reproduction link

https://echarts.apache.org/examples/zh/editor.html?c=calendar-heatmap

Steps to reproduce

1. Set the range of the calendar in the case to "999". This is because the console will report an error: TypeError: Cannot read property'slice' of undefined.
2. It is understandable if the time is less than 1000, but it will report an error if you continue to call setOption at this time: Uncaught Error: setOption should not be called during main process.
3. It is guessed that the error in the first step caused the state of the variable DEV in setOption to not be updated correctly, which made it impossible to call setOption again.

What is expected?

I hope that the error of the canlendar part of the code will not affect the normal use of setOption.

What is actually happening?

Some codes of canlendar report an error and setOption cannot be called again.

---

If you destroy the instance every time, and then call setOption, it can be used normally.

[bigfacewo]

截图补充：

[echarts-bot]

This issue is labeled with difficulty: easy.
@bigfacewo Would you like to debug it by yourself? This is a quicker way to get your problem fixed. Or you may wait for the community to fix.

Please have a look at How to debug ECharts if you'd like to give a try. 🤓

[fuchunhui]

According to ISO 8601, you must type year in four-digit to avoid Y2K, It represents years from 0000 to 9999.

how to fix this issue, it depends on whether echarts should support it or not.

perhaps some ways:

1. using '0999' instead of '999'.
2. not support less than 1000.
3. still 999, adjust /^\d{4}/ to /^\d{1,4}/, and fix error by two-digit year.

[bigfacewo]

@fuchunhui Thanks!
In fact, my problem is not whether I need to support a time format like 999. In my system, for example, my initial value 2021, when the user wants to modify it to 2020, he needs to delete the 1 at the end first, and then it becomes 202, which will cause this error. When he continues to enter 0, it becomes 2020, but because of the above error, he cannot render the chart again, Maybe we can avoid this problem by use debounce, but I think this problem should be solved by echarts.