diff options
| author | silverwind <me@silverwind.io> | 2024-03-15 10:13:01 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-03-15 09:13:01 +0000 |
| commit | 0d3ec8e2adfcf49329b52d74367698b62ffb3f73 (patch) | |
| tree | b8977fd611f107ab651771e991f591fc16e2d804 /cmd/admin_auth_ldap_test.go | |
| parent | 277f90d4164c09dc42a0fc6b1041147e76874f41 (diff) | |
| download | gitea-0d3ec8e2adfcf49329b52d74367698b62ffb3f73.tar.gz gitea-0d3ec8e2adfcf49329b52d74367698b62ffb3f73.zip | |
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.
Diffstat (limited to 'cmd/admin_auth_ldap_test.go')
0 files changed, 0 insertions, 0 deletions