You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems to have been avoided through [dev-dependencies], but this is not a good solution since rust-analyzer reports it as an error.
Feasible solution:
Extract the IT of Xline (which may include curp and client's IT) as a separate sub crate.
Or
Put xline-test-utils into xline and add #[cfg(test)] to its module:
// For test binary with `--features test` or test target#[cfg(any(test, feature = "test"))]#[cfg_attr(feature = "test", allow(unused))]pubmod test_util;
Version
0.6.1 (Default)
Relevant log output
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Hi, I found a related issue in rust-analyzer repo #rust-lang/rust-analyzer/issues/14167, where the author indicated that we can safely ignore this error in our situation if everything works fine.
It is not a wrong thing to do that, it's just r-a struggling with it (so yes, you are hitting this here). If everything works fine you can safely ignore the error.
Description about the bug
From rust-analyzer:
It seems to have been avoided through
[dev-dependencies]
, but this is not a good solution since rust-analyzer reports it as an error.Feasible solution:
Extract the IT of Xline (which may include curp and client's IT) as a separate sub crate.
Or
Put xline-test-utils into xline and add
#[cfg(test)]
to its module:Version
0.6.1 (Default)
Relevant log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: