mirror of
https://github.com/go-gitea/gitea
synced 2024-09-12 12:19:38 +02:00
Follow #21429 & #22861 Use `<gitea-locale-number>` instead of backend `PrettyNumber`. All old `PrettyNumber` related functions are removed. A lot of code could be simplified. And some functions haven't been used for long time (dead code), so they are also removed by the way (eg: `SplitStringAtRuneN`, `Dedent`) This PR only tries to improve the `PrettyNumber` rendering problem, it doesn't touch the "plural" problem. Screenshot: ![image](https://user-images.githubusercontent.com/2114189/229290804-1f63db65-1e34-4a54-84ba-e00b44331b17.png) ![image](https://user-images.githubusercontent.com/2114189/229290911-c88dea00-b11d-48dd-accb-9f52edd73ce4.png) |
||
---|---|---|
.. | ||
GiteaLocaleNumber.js | ||
GiteaOriginUrl.js | ||
README.md | ||
webcomponents.js |
Web Components
This webcomponents
directory contains the source code for the web components used in the Gitea Web UI.
https://developer.mozilla.org/en-US/docs/Web/Web_Components
Guidelines
- These components are loaded in
<head>
(before DOM body), so they should have their own dependencies and should be very light, then they won't affect the page loading time too much. - If the component is not a public one, it's suggested to have its own
Gitea
orgitea-
prefix to avoid conflicts.
TODO
There are still some components that are not migrated to web components yet:
<time data-format>