geldata / geldata/gel-editor-plugin
Requires VSCode restart after a schema migration
Open
bug
- Dominant language
- JavaScript
- Stars
- 37
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Description
We received this review on the VSCode extension marketplace:
> Excellent. The only issue is it seems to require the program to be restarted each time a database migration occurs.
Is there anything we can do to mitigate this?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the VSCode extension behavior before and after a database migration, then trace how the extension obtains or refreshes schema information. Done means the extension reflects a completed migration without requiring VSCode to restart.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, vscode
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100