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

feat: ability to use user provided tslint config #159

Merged
merged 2 commits into from Jun 1, 2018

Conversation

ofrobots
Copy link
Contributor

@ofrobots ofrobots commented Jun 1, 2018

This change adds the ability to use tslint.conf provided by the user.
If the user doesn't have a config file, we fall back to the default
gts config file.

This depends on #158, so ignore that commit when reviewing. That commit will be removed once #158 lands.

We do prefer the user-provided config file over the default now, which is potentially breaking, but I doubt users ever had the reason to have a local tslint.json before. I don't think this is semver major, but feel free to push back.

@codecov-io
Copy link

codecov-io commented Jun 1, 2018

Codecov Report

Merging #159 into master will increase coverage by 0.74%.
The diff coverage is 100%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #159      +/-   ##
==========================================
+ Coverage   96.01%   96.75%   +0.74%     
==========================================
  Files          10       10              
  Lines         326      339      +13     
  Branches       22       24       +2     
==========================================
+ Hits          313      328      +15     
+ Misses         13       11       -2
Impacted Files Coverage Δ
src/lint.ts 100% <100%> (ø) ⬆️
test/test-lint.ts 100% <100%> (ø) ⬆️
test/test-kitchen.ts 100% <0%> (+2.27%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0fd3a2d...2e6c9e8. Read the comment docs.

Copy link
Collaborator

@JustinBeckwith JustinBeckwith left a comment

Choose a reason for hiding this comment

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

Should we document this in the README in the same commit?

This change adds the ability to use tslint.conf provided by the user.
If the user doesn't have a config file, we fall back to the default
gts config file.
@ofrobots
Copy link
Contributor Author

ofrobots commented Jun 1, 2018

@JustinBeckwith added some wording in the README. PTAL.

@JustinBeckwith
Copy link
Collaborator

LGTM!

@ofrobots ofrobots merged commit e8cca36 into google:master Jun 1, 2018
@ofrobots ofrobots deleted the custom-tslint branch June 1, 2018 20:47
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.

None yet

4 participants