Different fluent localization files for different rust modules inside one localization domain

I have a crate that contains several modules for which I want to embed the localization resources

Suppose my crate is structured as:
-- lib.rs
-- mod1
---- file1.rs

I expect the i18n-embed system to search for localization files in

-- i18n/my-crate/mod1/file.ftl

But all it does ever consider is a single file `{domain.ftl}` (e.g. `my-crate.ftl`) which is used for all the tranlsation strings across my crate

Is there a way to avoid clumping of every single localized string into a single Fluent file?

The issue names lib.rs, mod1/file1.rs, and the expected i18n/my-crate/mod1/file.ftl path; start by tracing how localization resources are selected for the single domain.ftl file. Determine whether module-specific Fluent files are supported, and make the expected lookup behavior clear and verifiable.

Written by the indexing model from the issue text.