Introduce GiteaLocaleNumber custom element to handle number localization on pages. (#23861)
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:  
This commit is contained in:
parent
01d9466bfd
commit
19de52e0f4
24 changed files with 94 additions and 227 deletions
|
@ -54,13 +54,6 @@ export function parseIssueHref(href) {
|
|||
return {owner, repo, type, index};
|
||||
}
|
||||
|
||||
// pretty-print a number using locale-specific separators, e.g. 1200 -> 1,200
|
||||
export function prettyNumber(num, locale = 'en-US') {
|
||||
if (typeof num !== 'number') return '';
|
||||
const {format} = new Intl.NumberFormat(locale);
|
||||
return format(num);
|
||||
}
|
||||
|
||||
// parse a URL, either relative '/path' or absolute 'https://localhost/path'
|
||||
export function parseUrl(str) {
|
||||
return new URL(str, str.startsWith('http') ? undefined : window.location.origin);
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue