Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Annotations reported on the wrong lines in the PR
See original GitHub issueTest repository PR: https://github.com/nayaabkhan/graphql-inspector-pr-issue/pull/1/files
Observations:
- It seems that the lines for comments with
#are not accounted for. - The annotation of removal takes the line number from the older version and displays it on the position for the new version.
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
[Github] PR Decoration - Annotation on wrong line · Issue #189
On Github PR decoration, annotation for single line issues are reported on the wrong line, because end line of the annotated error is ......
Read more >Exposing ktlint report as GitHub PR annotations - hrach.dev
So the (ktlint) formatter should handle adding/updating the annotations. This is a potential way and lot of tooling uses it.
Read more >GitHub Checks - Codecov
Annotations in the "Checks" Tab To see annotations, first, go to the Checks tab under any pull request. Look for a patch status...
Read more >Adding GitHub annotations with PHP-CS-Fixer - madewithlove
Enhancing failing GitHub actions builds with GitHub annotations and PHP-CS-Fixer. Here's a guide!
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I fixed it in #1372
https://github.com/kamilkisiela/graphql-inspector/pull/1372/files#annotation_159906321
#1400 I opened an issue to track it