-
Notifications
You must be signed in to change notification settings - Fork 31
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
Update to crossterm 0.20.0 #29
Comments
I'm not sure about reexporting. When you use termimad, you probably also directly use crossterm. |
Yeah, that part is definitely not necessary to fix this - just a possible path. I only suggest it since the |
I also often reexport types in my crates, but mostly when you don't need to use the other types directly. |
done: versions of Termimad 0.12.x are based on Crossterm 0.20 |
Thanks!! |
When using
crossterm 0.20.0
withtermimad 0.11.1
, I get the following error:It looks to me as if there were some breaking changes in the
crossterm
crate that just moved where the types live.termimad
should update their API to accept this new type, and possibly consider re-exporting the types that are expected to be used within the skin builder API so consumer crates don't have to worry about matching dependency versions.The text was updated successfully, but these errors were encountered: