Closed SleeplessOne1917 closed 3 months ago
I'm pretty sure that you're using both versions for some reason, I've experienced this on the past. Perhaps is a rustc bug, do you've run cargo update
? Please, try to run cargo update
, ensure that fluent-templates v0.10.0 is used and, remove the target/
folder and recompile, that worked for me.
I don't want to reexport fluent-templates to allow users to change their fluent-templates version when they want without depending on leptos fluent. For example, to use it on the server.
I ran cargo clean
to delete the target folder and cargo update
to update all deps and still have the issue. I even deleted everything under ~/.cargo/registry/src
, ~/.cargo/registry/index
, and ~/.cargo/registry/cache
and I'm still getting the issue.
I also tried making a fresh project with cargo leptos new -g leptos-rs/start
and added the leptos-fluent
and fluent-templates
dependencies to it. I ran into the same issue of the project using both v0.10.0 and v0.9.4 of fluent-templates
.
I think I found the issue: the commit on the master branch of this repo that updated the fluent-templates
dependency isn't in v0.1.17. I was able to get my project to compile fine when I used a local copy of this repo with the master branch, and the 0.1.17 release in github's release list says "1 commit to master since release".
The most recent commit to master was bumping the fluent-templates
dep to use v0.10.0. Therefore, 0.1.17 must not include the fluent-templates
0.10.0.
Thanks for investigate it. I'll relax the dependency and release a patch ASAP. Apoligies for my confusion here.
I updated my project to use
leptos-fluent
v0.1.17 andfluent-templates
v0.10.0. When I try to compile my project, I get this error:The collision appears to be happening because it's trying to look both for the
fluent-templates
0.9.4StaticLoader
and 0.10.0StaticLoader
. A look through myCargo.lock
file reveals the following:An examination of
leptos-fluent
's codebase doesn't show any use of v0.9.4 anywhere - all of the uses are for v0.10.0. I am fortunately able to get my project to compile if I knock myfluent-template
version down to 0.9.4, but I imagine you want to have users of this library use the latest version offluent-templates
when possible. To this end, it may be worth re-exporting thefluent-templates
crate from this crate so users don't have to add the dependencies separately and so it's easier to guarantee that dependents use compatible versions.