3 Commits

Author	SHA1	Message	Date
wxiaoguang	9b442172fb	[PORT] Fix toAbsoluteLocaleDate and add more tests (gitea#32387) ... --- Conflict resolution: None Done differently: Removed typescript types. (cherry picked from commit aee9801d468997ab3cce32978416b697d9df77a7)	2024-11-03 15:55:05 +01:00
wxiaoguang	bdd75c4b55	[PORT] Fix absolute-date (gitea#32375) ... --- Conflict resolution: Trivial (package.json package-lock.json) Done differently: Removed typescript types. (cherry picked from commit ce4d909bd693fe903761eb835f7661e476a937ca)	2024-11-03 15:55:02 +01:00
silverwind	1a17c39e00	Use `Temporal.PlainDate` for absolute dates (#29804) ... Use the upcoming [Temporal.PlainDate](https://tc39.es/proposal-temporal/docs/plaindate.html) via polyfill. If there is any remaining bugs in `<absolute-date>` this will iron them out. I opted for the lightweight polyfill because both seem to achieve our goal of localizeable absolute dates. - With [`@js-temporal/polyfill`](https://www.npmjs.com/package/@js-temporal/polyfill) chunk size goes from 81.4 KiB to 274 KiB - With [`temporal-polyfill`](https://www.npmjs.com/package/temporal-polyfill) chunk size goes from 81.4 KiB to 142 KiB Also see [this table](https://github.com/fullcalendar/temporal-polyfill?tab=readme-ov-file#comparison-with-js-temporalpolyfill) for more comparisons of these polyfills. Soon there will be [treeshakable API](https://github.com/fullcalendar/temporal-polyfill?tab=readme-ov-file#tree-shakable-api) as well which will further reduce size. (cherry picked from commit 0d3ec8e2adfcf49329b52d74367698b62ffb3f73)	2024-03-20 08:46:29 +01:00