Skip to content
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

Better range positions for reports #96

Merged

Conversation

csordasmarton
Copy link
Contributor

Closes #16

A TextDocument has a method to get word range at a given position
called getWordRangeAtPosition. If no range information is available
for a report we can use this method to get word position at the given
line + column position.

@csordasmarton csordasmarton added the enhancement New feature or request label Feb 21, 2022
@csordasmarton csordasmarton added this to the 1.3.0 milestone Feb 21, 2022
A `TextDocument` has a method to get word range at a given position
called `getWordRangeAtPosition`. If no range information is available
for a report we can use this method to get word position at the given
line + column position.
@csordasmarton csordasmarton force-pushed the better_range_position_for_reports branch from 2f5fb38 to 0e71c48 Compare February 21, 2022 11:48
Copy link
Collaborator

@Discookie Discookie left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Works very well! 🎉

@Discookie Discookie merged commit bcee07c into Ericsson:main Feb 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Ranges in plist files generated by Clang Tidy with CodeChecker are incomplete
2 participants