As for the manipulation of the language tag in the static part you can use GitHub - BartOtten/phoenix_live_head: HTML Head element manipulation for Phoenix Live View · GitHub
BartOtten
Yoga
Thanks. How would it be in this case of this code in root.html.heex (lib/example_web/components/layouts/root.html.heex):
<html lang="en">
?
<html data-dynamic-lang="{current_language}">
Is the data-dynamic- the magic part that will do it?
And then it will be rendered in the root.html.heex as:
<html lang="es"> or <html lang="de"> depending on the route?
Will it work for all live routes and both first html render and then the websocket connection?
0
Yoga
One more question, if you don’t mind.
Do you think the changes to make Phoenix Localized Routes compatible with Phoenix 1.7 are too complex and time consuming or you will figure it out in a couple of weeks?
I am asking because I can somehow postpone the language switching part of the app for a month or two or so, but if it will take longer e.g. 6 months I will probably need to use Laravel with GitHub - codezero-be/laravel-localized-routes: ⭐️ A convenient way to set up and use localized routes in a Laravel app. · GitHub because the translated url parts based on the language selected is too important for me.
0
BartOtten
In template (using “en” as default / fallback)
<html data-dynamic-lang="{dynamic}" lang="en">
There is no magic detection of locale. You should get that value by other means (for example custom assignment from Localized Routes)
In the Live View:
socket
|> Phx.Live.Head.push("html", :set, "lang", assigns.loc.locale)
0
BartOtten
Localized Routes can already be used with Phoenix 1.7 when using the former default method of using the route helpers. It only lacks support at this moment for the new verified routes.
As changing helpers to verified routes might be just as much work as changing verified routes to localized verified routes, I’d say: use the Phoenix route helpers as we all have done in the previous decade.
ps. working on that 1.7 example.
1
BartOtten
Turns out, too much has changed to be 100% compatible. Modules have been renamed and so on. Will work on the 1.7 compatible version soon.
0