Skip to content
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

Fix README.md: remove one more set of curly brackets #91

Merged
merged 2 commits into from
Jun 3, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
34 changes: 16 additions & 18 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -72,22 +72,20 @@ To do so, add option `'allowComments'` or `{allowComments: true}`

For instance:
```js
{
import json from "eslint-plugin-json";

export default [
{
files: ["**/*.json"],
plugins: { json },
processor: "json/json"
"rules": {
"json/*": ["error", "allowComments"],
// or the equivalent:
"json/*": ["error", {"allowComments": true}]
}
},
];
}
import json from "eslint-plugin-json";

export default [
{
files: ["**/*.json"],
plugins: { json },
processor: "json/json"
"rules": {
"json/*": ["error", "allowComments"],
// or the equivalent:
"json/*": ["error", {"allowComments": true}]
}
},
];
```

### Custom Configuration (Legacy ESLint Format)
Expand Down Expand Up @@ -165,7 +163,7 @@ which the VSCode implementation provides by leveraging the

#### Will this plugin provide more configuration?

It is now possible as you can see in the [Configuration section](#custom-configuration)
It is now possible as you can see in the [Configuration section](#custom-configuration).

Additionally, support for autofixing common errors could be added in the feature.

Expand All @@ -175,4 +173,4 @@ Not really. `eslint` plugin interface wasn't designed to lint a completely diffe
its interface is flexible enough to allow it. So this plugin is certainly unusual.

Ideally, your editor would natively supports linting JSON. If it doesn't though, then might as well
use this plugin. Hacky linting is better than no linting :)
use this plugin. Hacky linting is better than no linting :).
Loading