-
Notifications
You must be signed in to change notification settings - Fork 697
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add support for JSON files in editors #1502
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Running this locally, I get package-lock.json
when I start up with 27.0.0 selected. Probably because we pull the content from https://github.com/electron/electron-quick-start/tree/27-x-y and that has a package-lock.json
.
Minor, but while you can't add a new file called |
2cb6c96
to
ad5966a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall LGTM. Somewhat of a nit, but can you swap some of the hardcoded 'package.json' text with PACKAGE_NAME
? It's nice to be consistent so searching finds all instances.
ad5966a
to
5127126
Compare
This PR adds support for JSON files. These can be used in Fiddle for data storage amongst other things - the impetus for this specifically is the ability to add
manifest.json
files for Chrome extensions.