-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reporters not working #3
Comments
Hey, cool that you found this project! |
Fixes #3 Update `ConsoleReporter` class to correctly handle findings and display their positions. * Change `ConsoleReporter` class in `asciidoc_linter/reporter.py` to use `error.position.line` instead of `error.line` to correctly access the line number. * Ensure `ConsoleReporter` class correctly handles the `position` attribute of `Finding` instances. --- For more details, open the [Copilot Workspace session](https://copilot-workspace.githubnext.com/docToolchain/asciidoc-linter/issues/3?shareId=XXXX-XXXX-XXXX-XXXX).
Do you think the PR could fix the issue? |
Dear @rdmueller ,
content of test.adoc
Test Environment Additional findings
Why I´m here? |
Hi @rdmueller, interesting project you started here! This is the repo I found searching for asciidoc linter.
When running on a file with findings, the current version is failing with errors like:
The issue maybe inconsistent classes/types. The reporters think they get LintReport (aka List LintError), while in fact they get List[Findings]. So either some processing step is skipped, or the reporters should use finding.position.line.
The text was updated successfully, but these errors were encountered: