Proactively inform users when there are updates available
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
Start by reading discussion #382 and tracing the existing lightbulb and Check For Updates flow for the libman.json example. Define the notification behavior and suppression semantics, including version ranges such as bootstrap@3.x; done means updates are surfaced proactively and users can suppress unwanted major-version notices.
Written by the indexing model from the issue text.
Description
Functional impact
This is a new feature request based on discussion in #382. Currently the only way to determine which libraries have new versions available is to place the cursor on each one in VS and wait for the lightbulb to show up. It would be better if we can surface it in some way so users can get a better sense of what is or isn't up to date.
Minimal repro steps
libman.json file:
{
"version": "1.0",
"defaultProvider": "cdnjs",
"defaultDestination": "Scripts/",
"libraries": [
{ "library": "jquery@3.3.0" }
]
}
Expected result
Something should automatically inform me that there's an update available (in this case jquery@3.3.1)
Actual result
The only way to learn of the update from the IDE is to invoke the lightbulb on the jquery entry, and invoke the Check For Updates from there.
Further technical details
This feature would also need a way to suppress notifications. For example, if I have bootstrap@3.x, I want to be able to suppress notifications about bootstrap@4.x until I consciously make the switch. This could possibly be a new property on the library entry ("checkForUpdates": false?}.
- Dominant language
- C#
- Stars
- 486
- Forks
- 91
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from aspnet/LibraryManager
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
aspnet/LibraryManager#824 · 1 comment · 3 reactions ·
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
aspnet/LibraryManager#804 · 2 reactions ·
-
Difficulty 1/5 Under an hour Newbie friendliness 48/100
aspnet/LibraryManager#829 · 1 comment · 3 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
aspnet/LibraryManager#820 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
aspnet/LibraryManager#808 · 5 comments ·
All issues in aspnet/LibraryManager
Similar issues
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Type: enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
apache/arrow-adbc#4809 ·
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
microsoft/vscode-azurefunctions#5197 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
microsoft/microsoft-ui-reactor#1274 ·