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
An additional related item to decouple the connector dep references is that fluvio-connector-common also referenced, is not a released crate, so it can't be referenced via crates.io
We definitely have a set of options with different tradeoffs to consider. Export as a feature adds adds bulk to the fluvio crate, but is nice that it keeps everything in sync for the end dep user.
What happened
cdk generate generates a project where the Cargo.toml contains fluvio (and fluvio related crate) dependency of:
Expected behavior
The generated project should create
How to reproduce it (as minimally and precisely as possible)
Steps to reproduce the behavior:
cdk generate <projectname>
cat projectname/Cargo.toml
Environment (please complete the following information):
cdk
Additional context
The immediate fix could be to change the template to refer to a stable fluvio.
The Cargo.lock would maintain the specific patch version.
The text was updated successfully, but these errors were encountered: