-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dependency issues when using unimock #26
Comments
Sorry, I was on vacation when this bug was filed, and I didn't get the notification. The thing is, entrait is a little out of date, and still uses |
Hi, thanks for the reply. Good to see that there is still activity here. Looking forward to the next version then. Is there a roadmap for entrait/unimock? |
I don't really have a roadmap. It's mostly ergonomic improvements and small tweaks I think, I haven't planned any major features. Lately I've focused more on Unimock, and when I think the |
OK, that is understandable. I am fine with entrait as it is, still looking
forward to improvement with unimock. Thanks for this fine piece of software.
…On Fri, 15 Sep 2023 at 12:41, Audun Halland ***@***.***> wrote:
I don't really have a roadmap. It's mostly ergonomic improvements and
small tweaks I think, I haven't planned any major features. Lately I've
focused more on Unimock, and when I think the 0.5 branch is in a good
state, I'll publish a new major entrait version. I'm working on this in my
spare time when I have time, development has slowed down a bit because it's
now more busy on my day job.
—
Reply to this email directly, view it on GitHub
<#26 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAQNG2BKMD7NDNJZYKAPGTX2QWENANCNFSM6AAAAAA2QR4AL4>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***>
|
entrait |
Closing this as fixed. |
Hi there, a couple of issues with dependencies I noticed. Thanks for this elegant library, I searched high and low for a solid dependency injection in Rust and this is the only one I think makes sense.
I use
cargo build --tests
to build.Using the unimock option for the entrait macro
Given this
cargo.toml
and this
main.rs
I get the error
error[E0433]: failed to resolve: could not find `__unimock` in `entrait
Using the unimock feature
When I switch to the unimock feature in
cargo.toml
things get better.Here is the
main.rs
for this caseStill, the compiler complains
no method named `each_call` found for struct `FooMock` in the current scope
What I did to work around this problem was to import
entrait::__unimock::*
instead ofuse unimock::*;
.Am I overlooking something (quite likely) or are these bugs?
The text was updated successfully, but these errors were encountered: