Feedback for v2 - patches.lock filename #485
Closed
Sweetchuck
started this conversation in
General
Replies: 1 comment
-
|
I would suggest that the contents of this file not be manipulated in a code editor, but I agree with this line of reasoning:
I have opened #492 to switch to |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello
I think the file name choice for
patches.lockis not the best,because by default none of the existing "text editors" or IDE provide syntax highlighting for this file.
I (and every developer) have to to re-configure all editors that I use (KATE, JEdit, Vim, PHPStorm, etc...) to recognize the
patches.lockfile as a regular JSON file.If the file content is a JSON then why not use the
.jsonfilename extension?I know that there is already
composer.lockfile name, which is already supported by most text editors.In my humble opinion that was also a bad choice, but way too late for that to change it :-)
Suggestions:
patches.lock.jsonpatches-lock.jsonBeta Was this translation helpful? Give feedback.
All reactions