-
Notifications
You must be signed in to change notification settings - Fork 41
Description
Hi everyone,
to organize my project, I split my project into several different crates, many of which require the labels provided by rust-i18n. Using the share-in-workspace example, I was able to get the functionality of the rust-i18n crate working quite easily.
I'm also using the very helpful i18n cli tool provided by this library. However, my main Cargo.toml file, configuring the workspace, does not define a package. The binary of the software lies in a separate crate. Because of that, I'm currently not able to configure the i18n cli tool, as this seems to be only configurable via a package:
[package.metadata.i18n]
# CLI tool configThis currently forces me to reorganize my project, move the binary file out of the subfolder, and additionally configure it in the main "Cargo.toml" file.
Instead, I would find it helpful to be able to also configure the tool via a workspace, for example:
[workspace.metadata.i18n]
# CLI tool configAlternatively, the tool could also be configured using a configuration file.
Does something like this make sense, or is there another way to configure the tool?