-
Notifications
You must be signed in to change notification settings - Fork 36
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
wierd interaction due to two twitch_types
crates used
#256
Comments
For future visitors, after the move from [dependencies]
# rev isn't required, but it's good to pin a specific revision
twitch_api = { git = "https://github.com/twitch-rs/twitch_api.git", rev = "340a582" }
# workaround for https://github.com/twitch-rs/twitch_api/issues/256
[patch.crates-io.twitch_types]
git = "https://github.com/twitch-rs/twitch_api.git"
rev = "340a582" # only if you pinned the repo to a specific revision If you don't want to rename every import of extern crate twitch_api as twitch_api2; |
It's also possible to do [dependencies]
twitch_api2 = {package = "twitch_api", ...} |
Oh didn't know that. It's much better than |
Just ran into this again. Maybe this should be a monorepo instead of using submodules? I'm not sure how releasing works then, however. |
I don't think monorepo solves it, since the source for the
|
Due to how we currently have
twitch_types
used intwitch_api2
andtwitch_oauth2
, there's a wierd interaction happening due to the two twitch_api crates used are not the same due to pathing.To circumvent the issue, users that have specified
twitch_api2
as a path or git dependency will need to do the following:this issue manifests as
Can this be solved neatly without requiring a patch?
The text was updated successfully, but these errors were encountered: