9aece2a7b8
Instead of generating a fluent.proto file with a giant enum, create a .json file representing the translations that downstream consumers can use for code generation. This enables the generation of a separate method for each translation, with a docstring that shows the actual text, and any required arguments listed in the function signature. The codebase is still using the old enum for now; updating it will need to come in future commits, and the old enum will need to be kept around, as add-ons are referencing it. Other changes: - move translation code into a separate crate - store the translations on a per-file/module basis, which will allow us to avoid sending 1000+ strings on each JS page load in the future - drop the undocumented support for external .ftl files, that we weren't using - duplicate strings in translation files are now checked for at build time - fix i18n test failing when run outside Bazel - drop slog dependency in i18n module
20 lines
635 B
Rust
20 lines
635 B
Rust
// Copyright: Ankitects Pty Ltd and contributors
|
|
// License: GNU AGPL, version 3 or later; http://www.gnu.org/licenses/agpl.html
|
|
|
|
pub mod protobuf;
|
|
|
|
fn main() {
|
|
protobuf::write_backend_proto_rs();
|
|
|
|
// when building with cargo (eg for rust analyzer), generate a dummy BUILDINFO
|
|
if std::env::var("BAZEL").is_err() {
|
|
let buildinfo_out =
|
|
std::path::Path::new(&std::env::var("OUT_DIR").unwrap()).join("buildinfo.txt");
|
|
std::fs::write(&buildinfo_out, "").unwrap();
|
|
println!(
|
|
"cargo:rustc-env=BUILDINFO={}",
|
|
buildinfo_out.to_str().expect("buildinfo")
|
|
);
|
|
}
|
|
}
|