Skip to content

support full path in call #6

@toejough

Description

@toejough

turns out the revision parsing needs an exact local path from the project root, or it filters results out...

openlynt -path pkg/<redacted>.go
[openlynt] filtered 7 violations in pkg/<redacted>.go due to revision limits
pkg/<redacted>.go:1688 violation of TODO/FIXME/XXX format: expected at least 2 lines of context but have 1

openlynt -path /Users/<redacted>/pkg/<redacted>.go
[openlynt] filtered 8 violations in /Users/<redacted>/pkg/<redacted>.go due to revision limits

We should support the full path in the call.

My immediate use case is for use with https://github.com/iamcco/diagnostic-languageserver. As-is, if I use the revision filter, the language server never calls any violations out. I can remove the revision filter, and then the language server sees the errors, but... there are a lot of them :-P

I could ask the diagnostic-languageserver folks to allow module-local paths, too, but we should support fully-specified paths anyway.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions