-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
TSC problem matcher doesn't handle line & column in errors #97
Labels
enhancement
New feature or request
Comments
I just ran into this again. Is it intentional that the line & column numbers aren't being included in the annotation? |
It looks like |
5 tasks
will track work to add line and column |
marcelgerber
added a commit
to owid/owid-grapher
that referenced
this issue
Sep 5, 2020
that detects the correct line number. This gives us nice annotations if any `tsc` errors occur in a PR, which helps track down issues. `actions/setup-node` already registers a `tsc` problem matcher, but theirs doesn't respect line numbers (actions/setup-node#97). Once that issue is fixed we can revert this commit.
krzyk
pushed a commit
to krzyk/setup-node
that referenced
this issue
Apr 11, 2023
…code WEEPKRK-447 show cpcode
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have a build at xt0rted/slash-command-action#71 that's failing and the typescript problem matcher is picking up the error, but it's not associating the annotation with the correct line as seen here. This looks to be due to line value also containing the column (
107,11
).This can be seen using https://regex101.com/ with the values:
The text was updated successfully, but these errors were encountered: