Force interface language by config file#792
Force interface language by config file#792DearRude wants to merge 1 commit intoPlume-org:mainfrom DearRude:force-lang
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #792 +/- ##
==========================================
- Coverage 39.09% 39.08% -0.01%
==========================================
Files 73 73
Lines 9756 9758 +2
Branches 2233 2233
==========================================
Hits 3814 3814
- Misses 4885 4887 +2
Partials 1057 1057 🚀 New features to boost your workflow:
|
|
The issue with the front-end is that it runs in the browser: it can't access the environment variables of the server. I think the solution would be to:
I hope this isn't too much. I can try to guide you more if need detailed steps, I know it can be hard to get started on a codebase you know nothing about. Feel free to ask me here or on Matrix if you have any questions. |
elegaanz
added
A: Backend
The feature is missing, so it's not the issue at hand, but doing just that was actually not sufficient. You must also rebuild Plume, as it's build script (build.rs) is the one copying files from |
|
I give up on this. Could not make it work... |
3 participants
As explained in #785, trying to force the language interface which specified in
.envfile.I tried the commented code below and re-compiled the front, but nothing happened. Since I didn't find any other piece which gets browser language, I assume my method of recompilation is flawed. (Only do
cargo web deploy -p plume-front --release)So I made this WIP PR as @igalic suggested. 😁