fix: optimization getLocaleDate performances

[Janlaywss]

Reason

Open the Gantt chart component, found the fps drop, only 23fps minimum

Through Chrome Devtools Performance analysis, it is found that longtask is more serious. And toLocaleDateString takes a long time:

The toLocaleDateString function takes a long time

the root cause seem to be that instantiates a new Intl.DateTimeFormat every time toLocaleString is called, which has a relatively high cost. (moment/luxon#352)

Solution

Since there will only ever be a very limited number of formats, those format instances should be cached after creation. This reduces the runtime of toLocaleString cost by a factor of 10.

Final Results

Through optimization, FPS has been improved by 10%. After the upgrade, the lowest reached 28fps

[MaTeMaTuK]

Thank you for help with optimisation!