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

improve generation of diagnostics, fix linter tests #268

Merged
merged 4 commits into from
Apr 23, 2019

Conversation

phryneas
Copy link
Contributor

@phryneas phryneas commented Apr 22, 2019

(feat) improve generation of diagnostics

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 #257

(fix) linter tests

actually use the correct useTypescriptIncrementalApi value for some of the linter tests that were using the default value before

(fix) linter tests that were doing nothing

fix a bug where, as tslint was set to true and the files being checked had no parent folder with a tslint.json, tslint never found any warnings
also fixes a failing test because a syntactic error was counted as linter warning

see discussion in #257

this is based off #253, so please merge that before you merge this :) (should also make the diff more readable)

@phryneas
Copy link
Contributor Author

(just force-pushed everything because I had the wording of the commit messages wrong 😁 )

@piotr-oles
Copy link
Collaborator

I'm afraid you are missing colon next to the type section (should be fix(tests): fix linter tests that were doing nothing) :) The history of commits is clear so I wouldn't like to squash them :)

Copy link
Collaborator

@piotr-oles piotr-oles left a comment

Choose a reason for hiding this comment

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

Great work :)

src/patchTypescript.ts Outdated Show resolved Hide resolved
src/patchTypescript.ts Outdated Show resolved Hide resolved
src/service.ts Outdated Show resolved Hide resolved
@phryneas
Copy link
Contributor Author

I'm afraid you are missing colon next to the type section (should be fix(tests): fix linter tests that were doing nothing) :) The history of commits is clear so I wouldn't like to squash them :)

Whoops! Will do a rebase & rename :)

@phryneas
Copy link
Contributor Author

Okay, I'll rebase this on the current beta and then we're good to go.

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
@phryneas
Copy link
Contributor Author

@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 beta? Wait for both of you to approve?

@piotr-oles
Copy link
Collaborator

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 :)

@johnnyreilly
Copy link
Member

johnnyreilly commented Apr 23, 2019

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!

src/patchTypescript.ts Outdated Show resolved Hide resolved
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
@phryneas phryneas dismissed johnnyreilly’s stale review April 23, 2019 17:12

guess I have to dismiss this to be able to merge? sorry -.-

@phryneas phryneas merged commit 7e74e05 into TypeStrong:beta Apr 23, 2019
@piotr-oles
Copy link
Collaborator

🎉 This PR is included in version 1.2.0-beta.4 🎉

The release is available on:

Your semantic-release bot 📦🚀

@johnnyreilly
Copy link
Member

This is great work @phryneas!

@piotr-oles what's the process now? We raise a PR to merge from beta to master?

@piotr-oles
Copy link
Collaborator

🎉 This PR is included in version 1.3.0-beta.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

@piotr-oles
Copy link
Collaborator

🎉 This PR is included in version 1.3.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants