Code Builder Extension Notification stays even after updating extensions
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- devtools
Research direction
No source files, tests, or code entry points are mentioned. Start by reproducing the issue in a new Code Builder instance: update all listed extensions, select “Reload Required,” and verify whether the notification glyph and update indicators remain. Done means the notification no longer reports extensions needing updates.
Written by the indexing model from the issue text.
Description
Describe the bug
Loaded a new Code Builder instance and saw a notification for 16 extensions that needed to be updated in the notification glyph. The issue is that after updating the extensions, the "16" notification glyph doesn't go away and the extensions still appear to need updates.
To Reproduce
Steps to reproduce the behavior:
- Install Code Builder
- Create a new Code Builder instance
- After loading, notice the 16 notification glyph that there are extensions that need to be updated
- Update all extensions
- Click
Reload Required - After updating all extensions, notice the 16 notification glyph is still visible
Expected behavior
After updating all extensions, it should no longer show a notification glyph that there are extensions that need to be updated given that we updated them.
Screenshots
After updating, see screenshot
Desktop (please complete the following information):
- OS: Mac OS Ventura 13.5.1
- Browser: Chrome
- Version: 117.0.5938.149
Additional context
Add any other context about the problem here.
- Dominant language
- No language data
- Stars
- 35
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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 forcedotcom/code-builder-feedback
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
forcedotcom/code-builder-feedback#273 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
forcedotcom/code-builder-feedback#265 · 2 comments ·
-
type:enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
forcedotcom/code-builder-feedback#262 · 1 comment ·
All issues in forcedotcom/code-builder-feedback
Similar issues
-
kaliscan.com OpenN: AdGuard for iOS P3: Medium T: Ads
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
AdguardTeam/AdguardFilters#242501 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
[BUG] createTool tools cannot be registered with Mastra when exactOptionalPropertyTypes is enabled Opencustomer-eng status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
add-toolnames MCP Toolnames Toolnames checkup
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
rajbos/ai-engineering-fluency#2190 · 3 comments ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
gajus/eslint-plugin-jsdoc#1776 · 1 reaction ·