-
-
Notifications
You must be signed in to change notification settings - Fork 239
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
improve generation of diagnostics, fix linter tests #268
Conversation
b1d57a7
to
59247b7
Compare
(just force-pushed everything because I had the wording of the commit messages wrong 😁 ) |
I'm afraid you are missing colon next to the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work :)
Whoops! Will do a rebase & rename :) |
59247b7
to
ab0f586
Compare
ab0f586
to
2709397
Compare
Okay, I'll rebase this on the current |
actually use the correct `useTypescriptIncrementalApi` value for some of the linter tests that were using the default value before
fix a bug where, as `tslint` was set to true and the files being checked had no parent folder with a tslint.json, tslint in these tests never found any warnings also fixes a failing test because a syntactic error was counted as linter warning
2709397
to
17d7440
Compare
@piotr-oles @johnnyreilly Oh, seeing that I can now merge PRs myself: what is my mode of operation here? Wait for one of you two to approve the changes, then merge into |
For me one approve is enough for fixes and small improvements :) For breaking changes and new features I think it will be better for all of us to get review from two different developers :) |
That's a sensible general approach I think. 👍 The flip side of that is that it's important that reviews happen in a timely fashion. So if someone has asked me for a review and I haven't come back to them in a reasonable period of time, they should feel free to keep shipping.😁🛳️ BTW feel free to merge this when you've added the comment I requested @phryneas! |
when the options `checkSyntacticErrors: false` and `useTypescriptIncrementalApi: true` both were active, no semantic errors were emitted as soon as the first syntactic error was encountered this patches the `typescript` import to override that behavior see discussion in TypeStrong#257
17d7440
to
ae80e5f
Compare
guess I have to dismiss this to be able to merge? sorry -.-
🎉 This PR is included in version 1.2.0-beta.4 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This is great work @phryneas! @piotr-oles what's the process now? We raise a PR to merge from |
🎉 This PR is included in version 1.3.0-beta.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
🎉 This PR is included in version 1.3.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
(feat) improve generation of diagnostics
(fix) linter tests
(fix) linter tests that were doing nothing
see discussion in #257
this is based off #253, so please merge that before you merge this :) (should also make the diff more readable)