TimeScaleTimeOptions requires parser

[rtmotiondev]

Expected behavior

parser in TimeScaleTimeOptions should be optional.

Current behavior

Why is parser a required field for TimeScaleTimeOptions?

When using a date adapter like chartjs-adapter-date-fns, everything is already set up, so there’s no need to specify the parser again. However, in this case, we are forced to do so, and there’s no clean way to obtain the underlying parser.

        const scaleFormat: TimeScaleTimeOptions = {
            unit: "year",
            displayFormats: {
                month: "yy",
            },
            tooltipFormat: "eeee, MMM dd, yyyy",
            parser: ??,
            round: false,
            isoWeekday: false,
            minUnit: "millisecond"
        };

"chart.js": "^4.4.7",
"chartjs-adapter-date-fns": "^3.0.0",

Reproducible sample

https://www.typescriptlang.org/play/?#code/JYWwDg9gTgLgBAbzgYQBYENYBo4BVQCmAygMboA2B+IBA8mDMBAHYDOcAvnAGZQQhwA5CQywAdACtWggNwBYAFCKA9MrgB1VAWZwArq2DMA5nHRwAJuhgFTlhgShxywANY2RmGFIC06O9ahvS2tvbjY4AgA3BwBPGFRDE2B2CigCPxi4VgIYXTAsiDh4hwJBdmZC5gICcyLC1jACEmBuTOK4MExsx3QjdEMxOEUSFlZ4VjJKADFoECsALjxCUgoqQnpGUbgAXkRFOAO9ZmAYRYAiGPSoM6x9w-NksHJ0GJmoOZhWRYQ7w8OQFjxc4xGI3X6cW4KP4wCAQciMMBvD7narVHAAWUxFnMOBBILBUMOnSg3XOBL+fF0zHMi24FGykL+yQg6mqLksMVp9IIjP+hgAqsdTnAziBgORnNkRtSzooOPIlIrIpg4CQYAAPHYWCAkXQ0ZgwMRGHIAUUo+pgACEYgBJcwAClFMTQnjOAEpTOwABK4dEAGWQ6GYytYZoIFoVyscIGdonguyqAHcUHH7Wr1TgfoSDjAYo1FoJnFVBLyDsF0N9wX9ngAjAjkL5wADaZwASjUbiLLeRdARO2cAJr18gQRP9gDiaW0-YACrooE8+zgzrQoEHjWcALqlv4WKzobKfRZNrO7s9OdB18gFgDEcAg3DgADUINZpDvz3uYBXmwBGABMOC-gAnDgADMOAAKw4IBcBgduVaHBwm7ghwO4QAwTBsJW2aHBMqyNqe57qjhn4HIhBxoRRcCcnsuFntRHCIUxuEsRwboyEAA

Optional extra steps/info to reproduce

No response

Possible solution

No response

Context

Using chartjs with Typescript in strict mode

chart.js version

4.4.7

Browser name and version

No response

Link to your project

No response