[chore] move compiler warnings/errors to dedicate files #6503
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
dummdidumm
reviewed
Jul 7, 2021
| @@ -21,6 +21,9 @@ | |||
| "resolveJsonModule": true, | |||
| "allowSyntheticDefaultImports": true, | |||
|
|
|||
| // Hides exports flagged with @internal from the d.ts output | |||
| "stripInternal": true, | |||
There was a problem hiding this comment.
This should help us not leaking internal API
Closed
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.
This organizes all compiler errors and warnings into separate files. This should help discoverability of those and know where to look them up in a distinct place. It also reduced some duplication.
Before submitting the PR, please make sure you do the following
[feat],[fix],[chore], or[docs].Tests
npm testand lint the project withnpm run lint