* new settings work
* Polishing work on settings refactor
* Run intl:extract
* List view -> Rows view
* Remove current preferred system theme indicator to make the themes fit on one line
* Remove extra margin on top of navstack
* Convert default.vue to composition API
* Add translations to default page layout
* Generate index.json
* Fix sign up page
* Generate index.json
* Fix atUserLabel
* Fix composition API port
* Follow-up fixes for #1616 (#1618)
* Re-organize default layout messages
- Group some of the messages by their appearance (like banners)
Grouping makes avoids having to think too much about the property
names, keeps declarations clean, and also can be minified better,
since variable names, unlike property names, can be easily mangled.
- Remove needless type specification in property name[^1]
It's already clear from where the message is formatted what it does,
and if you need clarification, you can Ctrl+hover and see the type in
the key.
- Change some keys to conform to conventions
We generally follow the pattern location > kind?. Things like 'label'
are unnecessary, as everything is assumed to be label by default; the
same applies to things like 'button', which are also often unnecessary
as they're part of the location compound.
- Remove message for handle, which should not be translatable
It's very unlikely user handle format changes between any of the
locales.
[^1]: Common messages are pending restructuring that would fix this
* Fix navRoutes not being computed in default layout
* Fix untranslated Get Modrinth App buttons in default layout
* Make legal disclaimer in the default layout translatable
It wouldn't make much sense to leave it untranslated since it is meant
for the end users too. It is also so small that it's unlikely to be
mistranslated.
* Extract missed legal disclaimer message from default layout
* Make SEO strings in default layout translatable
---------
Co-authored-by: Sasha Sorokin <10401817+brawaru@users.noreply.github.com>
* Begin Work
* More work
* Fix lint error
* More work on label
* Fix mistake
* Finish adding delete pat modal keys
* More label and button
* More label keys
* Fix lint error
* Description key
* Finish page
* Forgot this
* Fix lint error
* Add to navstack
* Apply suggestions from brawaru
* Normalization
* Re-organize PATs page messages (#10)
- Group messages by their usage
- Fix spelling mistakes in some of the property names and keys
- Change some of the keys to conform to keying conventions
- Change variable name in token.expires-in message to inTime
* Regenrate index.json
---------
Co-authored-by: Sasha Sorokin <10401817+brawaru@users.noreply.github.com>
* Begin Work
* WIP
* WIP
* WIP
* Use error notification keys
* Finish & fix error
* Fix lint error
* Normalize message IDs (#9)
It makes sense to compose message IDs in order:
- Place (page, sub page / "modal")
- Thing
- (optionally) Relation to the thing
For example, a label for a password field would be:
- auth.sign-in (on sign-in subpage of auth)
- password (password field)
- label (is a label for the field)
Another example - button to sign in:
- auth.sign-in
- action (this is an action to do something)
- sign-in (action to sign in)
This helps keep the IDs closer to the actual structure of the page,
oftentimes smaller in the code, and easier to understand by translators.
---------
Co-authored-by: Sasha Sorokin <10401817+brawaru@users.noreply.github.com>
Co-authored-by: Prospector <6166773+Prospector@users.noreply.github.com>
* Begin Work
* Begin Work
* WIP
* Finish Work
* Fix lint error
* Re-organize keys on E-mail verification page (#12)
- Group messages by the step
- Use simpler keys for message properties as they're not public
- Change message keys to conform to conventions
---------
Co-authored-by: Sasha Sorokin <10401817+brawaru@users.noreply.github.com>
Co-authored-by: Prospector <6166773+Prospector@users.noreply.github.com>
