Skip to content

πŸ’­ Spike: Define path to @eslint/jsonΒ #1612

@michaelfaith

Description

@michaelfaith

Overview

We've been largely kicking the can down the road on #655 due to no having a well-defined path for how to get there. In order to help unblock that work and also to provide some clarity for us and for the consumers of the package, I'd like to spend some time working out a strategy for how to get from where we are today (using jsonc-eslint-parser) to using the first-party @eslint/json language.

Ideally, I would like this to be a big part of our 2.0 release cycle.

Metadata

Metadata

Assignees

Labels

area: documentationImprovements or additions to docs πŸ“type: featureNew enhancement or request πŸš€

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions