micro-editor / micro-editor/micro

Put output of lint into log

Open
#1,191 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
29.6k
Forks
1.4k
Avg merge
2d 18h
Merged PRs (30d)
10

Description

Description of the problem or steps to reproduce

It would be really nice if the output from lint, in addition to being processed would also go into
the log.
I encountered a problem where the output from lit didn't fit the required format, so nothing
was shown. I wasn't sure that lit had actually run. It would be much easier to handle such
problems if lint put everything in the log.

Specifications

Commit hash: 1013b03
OS: OSX 10.11.6
Terminal: iTerm2

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file or test is named; start by locating the lint integration and how its output is currently processed and written to the log. Confirm that output which does not match the expected format is still preserved, while existing lint processing continues to work.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli, tooling
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.