New features #63
Replies: 3 comments 2 replies
-
Since Astro is getting baked in support for i18n based routing (see this RFC). I think it'll be great to integrate the changes into this library. As I understood it would make the generate pages script obsolete. |
Beta Was this translation helpful? Give feedback.
-
I've also been cooking up support for localized content/collections (.md/.mdx files) since translating blog/news posts via json is awkward. I'd be willing to contribute this functionality once I'm done on my current project (probably in 1-2 months). I think it would make this library a more complete solution to astro localization |
Beta Was this translation helpful? Give feedback.
-
Support for |
Beta Was this translation helpful? Give feedback.
-
If you want to help out developing new features here's what's planned :
root
.root
,srcDir
andtrailingSlash
).run
option in the config with aserialization
option, values could be"none"
,"page"
,"minimal"
."none"
would be the same asrun: "server"
,"page"
would be the same asrun: "client+server"
and"minimal"
would only serialize what has been used for the current page (see Question about client-side translations #62 ).t
options, for examplet("key", undefined, { group: "common" })
. The type generation should give auto-completion for your available groups. Maybe a special string such as"page"
could be used to reference the current page more easily.astro-i18n
.This post will be edited to add new features or delete the ones that have been developed.
Nothing is set in stone so we can discuss the implementation if you think that you have a better idea.
If you want to add another feature please contact me first, you can reply here or open a new discussion.
Beta Was this translation helpful? Give feedback.
All reactions