Config overwritten after 3.0 update
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 44.7k
- Forks
- 3.6k
- Avg merge
- 21m
- Merged PRs (30d)
- 1
Description
- I am on the latest Hyper.app version
- I have searched the issues of this repo and believe that this is not a duplicate
- OS version and name: Windows 10 1809
- Hyper.app version: 3.0.0 stable
- Link of a Gist with the contents of your .hyper.js: default config
- Relevant information from devtools (CMD+ALT+I on macOS, CTRL+SHIFT+I elsewhere): N/A
- The issue is reproducible in vanilla Hyper.app: Vanilla
Issue
Hyper automatically updated to 3.0.0.
When I opened Hyper this morning I got the Vanilla hyper.js without any config. After checking the %APPDATA/Hyper folder I found that my config was overwritten with the default.
As far as I understand the release notes this should have been fixed by canary10
https://github.com/zeit/hyper/releases/tag/3.0.0-canary.10
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
Start by reviewing the Hyper 3.0.0 update behavior around the .hyper.js file in %APPDATA/Hyper, and compare it with the 3.0.0-canary.10 release notes. Reproduce an update using a customized config; done means the existing user configuration remains intact instead of being replaced by the vanilla hyper.js.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100