Fix: ratatui version #311
Open
Fix: ratatui version #311
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The `[email protected]` uses not fixed `ratatui` version, which prompts for updates whenever a new version is released. So, it's better to uses the version `0.6.1` of the tui-textarea where the ratatui version is fixed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why
Following @OmegaTymbJIep it resolves #259. Basically, if fails on installation of the latest version of the corset -- it seems like the problem is the same as in #214.
The [email protected] uses [email protected] while corset uses [email protected]. The funny thing is the
[email protected]'s Cargo.toml (you can line below here):It means that whenever a new version of ratatui is released, the [email protected] dependency asks for a higher version. It's been released a new version and now they aren't compatible
What
Bumping the version of tui-textarea to v0.6.1 (the latest) it seems like plenty of bugs have been fixed since. That will cause the bumping of ratatui to v0.28.1 and crossterm to v0.28.1, but it breaks nothing - it's completely backward compatible.
Note: it will resolve this problem finally, as in the latest version of tui-textarea the version of ratatui is fixed to v0.28.0.
Prepared by @OmegaTymbJIep and @distributed-lab