Skip to content

planned stuff #1

@suo

Description

@suo
  • message when no lint errors
  • exclude globs
  • files_cmd argument
  • take argument (linter selection)
  • Paths should be canonicalized for all internal operations
  • Paths should always be displayed relative to user cwd
  • Pattern matching in lint config should be relative to lint config location
  • Automatically do not lint changes that come from "public" commits (i.e. commits in master)
  • progress indicators for longer running linters?
  • figure out if there's any way to make clang-tidy not take forever and generally be bad
  • filter lint results by files requested. Sometimes linters (looking at you clang-tidy) will report errors in files that you did not ask for.
  • Write some tests lol
  • Set up CI + releases
  • Maybe: swap to libgit2 instead of running git commands directly?
  • lintrunner init should support skip and take as well.
  • when run with -a signal to the user somehow that it worked.
  • have a default message to the user that they can run -a when there are available lints to apply
  • json output for machine consumption
  • insulate core from linter adapters failing
  • do a pass over lintmessage format (remove code and bypasschangedlinesfiltering arguments)
  • clangtidy: detect that we need to re-run the codegen stuff
  • Pass verbose through -v
  • panic_human
  • Should be able to pass paths, overriding changed files detection
  • add --rev arg
  • Nicer looking spinners (move the status to the left side)
  • Be able to apply patches from multiple linters to a single file.
  • make sure examples work and test that they do
  • Merge-base command (e.g. lint all changes between the merge-base with X branch and HEAD)
  • Formatting lints should display individual lint messages for each cluster of changes in the diff
  • rage command

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions