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
in sea-query-binder, the time crate version is set as <0.3.35 (i.e., time = { version = "<0.3.35",...}).
Is there any reason for this?
It does cause some understandably unforeseen behavior when the lib/app code relies on 0.3.
It seems to work, but tools like cargo outdated completely break for example, and might have other side effects.
Steps to Reproduce
Have sea-query with sea-query-binder with time
have another time = "0.3' in the Cargo.toml
cargo install cargo-outdated and then cargo outdated. The issue is that if this break, there might be more side effecs.
Expected Behavior
time set to version 0.3 or 0.3.35.
Actual Behavior
time set to version <0.3.35.
Versions
In sea-query-binder version 0.6.0-rc.2,
The text was updated successfully, but these errors were encountered:
Description
In
sea-query-binder
version0.6.0-rc.2
,in sea-query-binder, the
time
crate version is set as<0.3.35
(i.e.,time = { version = "<0.3.35",...}
).Is there any reason for this?
It does cause some understandably unforeseen behavior when the lib/app code relies on
0.3
.It seems to work, but tools like
cargo outdated
completely break for example, and might have other side effects.Steps to Reproduce
time = "0.3'
in theCargo.toml
cargo install cargo-outdated
and thencargo outdated
. The issue is that if this break, there might be more side effecs.Expected Behavior
time
set to version0.3
or0.3.35
.Actual Behavior
time
set to version<0.3.35
.Versions
In
sea-query-binder
version0.6.0-rc.2
,The text was updated successfully, but these errors were encountered: