Skip to content
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

yewtil 0.2.0 is in conflict with yew 0.16.0 #1233

Closed
1 of 3 tasks
agausmann opened this issue May 15, 2020 · 4 comments
Closed
1 of 3 tasks

yewtil 0.2.0 is in conflict with yew 0.16.0 #1233

agausmann opened this issue May 15, 2020 · 4 comments
Labels

Comments

@agausmann
Copy link

agausmann commented May 15, 2020

Problem

When trying to use the most up-to-date versions of yewtil and yew, I get a dependency conflict:

error: failed to select a version for `bincode`.
    ... required by package `yew v0.16.0`
    ... which is depended on by `phr-frontend v0.1.0 (/home/adam/dev/phr/frontend)`
versions that meet the requirements `~1.2.1` are: 1.2.1

all possible versions conflict with previously selected packages.

  previously selected package `bincode v1.0.1`
    ... which is depended on by `yew v0.10.0`
    ... which is depended on by `yewtil v0.2.0`
    ... which is depended on by `phr-frontend v0.1.0 (/home/adam/dev/phr/frontend)`

failed to select a version for `bincode` which could resolve this conflict

Steps To Reproduce

Create a project that depends on yewtil v0.2.0 and yew v0.16.0:

[dependencies]
yew = "0.16.0"
yewtil = "0.2.0"

Expected behavior

I expect to be able to use the latest version of all official crates together, I don't want to downgrade yew and lose features/improvements just to be compatible with yewtil.

Environment:

  • Yew version: yew v0.16.0
  • Rust version: rustc 1.45.0-nightly (769d12eec 2020-05-12)
  • Target: wasm32-unknown-unknown
  • stdweb / web-sys version: web-sys v0.3.39
  • OS: Linux 5.4.35_1
  • Browser: n/a

Questionnaire

  • I'm interested in fixing this myself but don't know where to start
  • I would like to fix and I have a solution
  • I don't have time to fix this right now, but maybe later
@agausmann agausmann added the bug label May 15, 2020
@jstarry
Copy link
Member

jstarry commented May 16, 2020

Thanks for the report @agausmann, I think the fix is as simple as releasing a new version of yewtil. @hgzimmerman could you help with that?

@jstarry
Copy link
Member

jstarry commented May 31, 2020

When updated, we should add a reference to send_future in the ComponentLink docs. Context: #1274 (comment)

@TheNeikos
Copy link
Contributor

As this seemed to have stalled a bit, I took the liberty to try and prepare the next release. I hope that was okay!

@siku2
Copy link
Member

siku2 commented May 18, 2021

This should be fixed now

@siku2 siku2 closed this as completed May 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants