Support returning lints as newline separated json objects
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.6k
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Description
When the linter tool in question returns the data as json in the first place, it doesn't really make sense to take that output and turn it into text lines, just for efm to parse that again.
Just wrangling the json around with something like jq is often much easier and less error prone.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating efm's existing linter-output parsing and the tests for JSON or line-based diagnostics. Trace how linter output is currently converted before efm parses it. Done means newline-separated JSON objects from a linter are accepted without requiring a text round trip; the issue does not name specific files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100