Don't delete local plugins when they are disabled
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 44.7k
- Forks
- 3.6k
- Avg merge
- 21m
- Merged PRs (30d)
- 1
Description
When a plugin is disabled, Hyper deletes it.
Personally I find this frustrating anyway, since it means I can't temporarily disable a plugin without it being deleted, but for local plugins it is doubly frustrating because it means development cannot take place in the plugin directory.
It would be nice if local plugins were not deleted when they are disabled.
Hyper 1.0.0
Electron 1.4.7
darwin x64 15.6.0
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.
Research direction
No file or test is named. Start by tracing how Hyper handles disabling plugins, then identify the path used for local plugins. Done means disabling a local plugin leaves its files in the plugin directory while the plugin remains disabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100