Skip to content

Conversation

@JamesHenry
Copy link
Member

@JamesHenry JamesHenry commented Jan 17, 2019

This builds on #34 and will not work until it does.

#34 has been merged

See #35 (comment)

and #35 (comment)

@JamesHenry JamesHenry added the DO NOT MERGE PRs which should not be merged yet label Jan 17, 2019
JamesHenry and others added 29 commits January 17, 2019 08:50
BREAKING CHANGE: This plugin now requires TSLint 5, and the user must now separately install and manage their own TSLint dependency

fix #3
@JamesHenry JamesHenry force-pushed the import-eslint-plugin-tslint branch from 1408708 to 74d628b Compare January 17, 2019 13:50
@JamesHenry JamesHenry removed the DO NOT MERGE PRs which should not be merged yet label Jan 17, 2019
@codecov
Copy link

codecov bot commented Jan 17, 2019

Codecov Report

Merging #35 into master will decrease coverage by 0.03%.
The diff coverage is 92.1%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master      #35      +/-   ##
==========================================
- Coverage   93.77%   93.73%   -0.04%     
==========================================
  Files          11       13       +2     
  Lines        1686     1724      +38     
  Branches      376      381       +5     
==========================================
+ Hits         1581     1616      +35     
- Misses         55       56       +1     
- Partials       50       52       +2
Impacted Files Coverage Δ
packages/eslint-plugin-tslint/src/custom-linter.ts 100% <100%> (ø)
packages/eslint-plugin-tslint/src/index.ts 90% <90%> (ø)

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 55867aa...494e247. Read the comment docs.

@JamesHenry
Copy link
Member Author

I have updated the plugin to not build its own TypeScript Program and leverage parserServices now that @uniqueiniquity's PR is in :)

Ben, I would be interested to know if this plugin is useful to you as you transition between TSLint and ESLint. I envisage it being useful for a hybrid state where some custom rules etc have not been converted.

Let me know your thoughts!

@JamesHenry
Copy link
Member Author

P.S. Docs are not up to date, I would like to update all the packages' docs at once before the first release from the monorepo

@JamesHenry JamesHenry requested a review from a team January 17, 2019 14:37
@armano2
Copy link
Collaborator

armano2 commented Jan 17, 2019

after @j-f1 finish working on tests for eslint with jest we should convert them in this package to (https://github.com/bradzacher/eslint-plugin-typescript/issues/242)

const tslintConfig = memoize(
(
lintFile: string,
tslintRules: RawRulesConfig,
Copy link
Collaborator

Choose a reason for hiding this comment

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

you can use Record<string, RawRuleConfig) here

@j-f1
Copy link
Contributor

j-f1 commented Jan 17, 2019

My current setup doesn’t use Jest, it just runs the tests directly in a loop.

@uniqueiniquity
Copy link
Contributor

@JamesHenry I absolutely agree about this plugin being useful as a transition tool, especially for custom rule sets that users or organizations may have.

@JamesHenry
Copy link
Member Author

It is 500ing when I try and rebase merge 😭

I have written to GitHub support

@JamesHenry JamesHenry merged commit 4ddbe89 into master Jan 17, 2019
@JamesHenry JamesHenry deleted the import-eslint-plugin-tslint branch January 17, 2019 19:12
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 21, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants