Add tsc problem matcher #9
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 3 commits
June 7, 2019 15:25
…eatures/problem-matchers
…eatures/problem-matchers
Closed
krzyk
pushed a commit
to krzyk/setup-node
that referenced
this pull request
Apr 11, 2023
adding a quick start section for new users
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
First problem matcher. We should think about what all we want.
IMO we should load
tscandeslintand leave the rest up to users. As I've thought more about this, I think we should stay away from test frameworks like mocha or jest because they are dependent on the reporter, so there's not a consistent format we can match against.