Versions of extensions
- Dominant language
- JavaScript
- Stars
- 60
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Description
I've rewritten an extension, so questions written for the old version will no longer work.
I also regularly have to use my local server to test new changes to an extension, so I don't inadvertently break other people's questions while debugging.
The editor should store multiple versions of extensions, and references to extensions should include the version. Declaring a new version should be an explicit step. There should be the option to always use the "development" version, but this should not be the default.
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or entry points are named. Start by locating how the editor stores extensions and how questions reference them, then trace the workflow for declaring a new extension version. Done means older references remain usable, version declarations are explicit, and a non-default development version can be selected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100