We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Use Case: i want to use that plugin for linting and auto-fix my json config file
Example Input:
{ "command": { "publish": { "conventionalCommits": true, "ignoreChanges": [ "**/__fixtures__/**", "**/__mocks__/**", "**/__tests__/**", "yarn.lock", "CHANGELOG.md" ], "message": "chore(release): publish" } }, "npmClient": "yarn", "packages": ["packages/*"], "version": "independent" }
Result:
6:12 error Parsing error: '{' expected
Root case: My Json file contain '*/' which make that plugin consider end of comment
Work around: Manually escape */
*/
{ "command": { "publish": { "conventionalCommits": true, "ignoreChanges": [ "*/fixtures/**", "*/mocks/", "**/tests/", "yarn.lock", "CHANGELOG.md" ], "message": "chore(release): publish" } }, "npmClient": "yarn", "packages": ["packages/*"], "version": "independent" }
The text was updated successfully, but these errors were encountered:
Thanks @davidnghk01 , will take a look into this, and get back to you 😄
Sorry, something went wrong.
jsonc plugin
FYI, turn out I find another plugin already done the json sorting feature
So I make use of that for my case ~
No branches or pull requests
Use Case:
i want to use that plugin for linting and auto-fix my json config file
Example Input:
Result:
Root case:
My Json file contain '*/' which make that plugin consider end of comment
Work around:
Manually escape
*/
{
"command": {
"publish": {
"conventionalCommits": true,
"ignoreChanges": [
"*/fixtures/**",
"*/mocks/",
"**/tests/",
"yarn.lock",
"CHANGELOG.md"
],
"message": "chore(release): publish"
}
},
"npmClient": "yarn",
"packages": ["packages/*"],
"version": "independent"
}
The text was updated successfully, but these errors were encountered: