Ask questionsShow different status indicator for semver-compatible updates
First let me say that I just recently discovered your extension on Twitter and I love it. That said, I think it could be better still, so here's one little suggestion.
Is your feature request related to a problem? Please describe. When reviewing dependency versions I'm usually hunting for semver-incompatible updates, since I use cargo update to bump all the semver-compatible ones. I noticed that your extension already shows 👍 for versions that are set to "1" for example, but actually it could/should also do this for crates that are set to "1.0.1" for example, since these are semver-compatible cargo will pull in the updates automatically. Setting it to 1.0.1 might be common if you've never tested your crate with 1.0.0 for example, or if you know you need a bugfix from 1.0.1. (Just in case you're not aware, in Cargo.toml "1.0.0" is equivalent to "^1.0.0" rather than "=1.0.0" -- you probably always want to be show semver-compatible updates in the latter case.)
Describe the solution you'd like Right now your extension either shows 👍 or "Latest: 1.2.3" by default. However, it seems to show "Latest: 1.2.3" even if I have say "1.1.2" configured. It would be nice if it could distinguish between semver-incompatible updates (as in, "2.0") and semver-compatible updates ("1.2.3"). The simplest way to do this could be to show 👍 for semver-compatible updates. A slightly more advanced way could be to distinguish between the case of semver-compatible and the case of semver-incompatible updates (for example, 👍 1.2.3 for semver-compatible and "Latest: 1.2.3" for -incompatible).
Answer questions serayuzgur
Hi All, Thanks for the issue. I am working on this right now. I think we should keep this issue at the safe area for now and parsing the lock file is whole new adventure. According to me shipping different semver indicators for the toml file first is best way to take fast action. I will share a table with you to understand the desired decorations on sample versions.
Related questionsNo questions were found.