Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

chore: the big package renaming#82

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
JamesHenry merged 7 commits intomasterfromnames
Jan 19, 2019
Merged

chore: the big package renaming#82

JamesHenry merged 7 commits intomasterfromnames
Jan 19, 2019

Conversation

JamesHenry
Copy link
Member

Consolidate everything under their new scoped names, yes this is unreviewable, but fortunately it is a one-off! :)

Better docs will follow after this before 1.0.0 tomorrow

j-f1 reacted with thumbs up emoji
@codecov
Copy link

codecovbot commentedJan 19, 2019
edited
Loading

Codecov Report

Merging#82 intomaster willnot change coverage.
The diff coverage is100%.

Impacted file tree graph

@@          Coverage Diff           @@##           master     #82   +/-   ##======================================  Coverage    94.8%   94.8%           ======================================  Files          48      48             Lines        2465    2465             Branches      380     380           ======================================  Hits         2337    2337             Misses         77      77             Partials       51      51
Impacted FilesCoverage Δ
...slint-plugin/lib/rules/prefer-namespace-keyword.js100% <ø> (ø)
...eslint-plugin/lib/rules/no-parameter-properties.js100% <ø> (ø)
packages/parser/src/visitor-keys.ts100% <ø> (ø)
packages/eslint-plugin/lib/rules/camelcase.js96.15% <ø> (ø)
.../eslint-plugin/lib/rules/member-delimiter-style.js100% <ø> (ø)
...lugin/lib/rules/no-angle-bracket-type-assertion.js100% <ø> (ø)
packages/eslint-plugin/lib/rules/no-namespace.js100% <ø> (ø)
...ges/eslint-plugin/lib/rules/no-inferrable-types.js92.1% <ø> (ø)
...ackages/eslint-plugin/lib/rules/member-ordering.js96.72% <ø> (ø)
...s/eslint-plugin/lib/rules/no-non-null-assertion.js100% <ø> (ø)
... and29 more

Continue to review full report at Codecov.

Legend -Click here to learn more
Δ = absolute <relative> (impact),ø = not affected,? = missing data
Powered byCodecov. Last update78a8b7c...5d9c2f8. Read thecomment docs.

@@ -40,7 +40,7 @@ ruleTester.run('tslint/config', rules.config, {
valid: [
{
code: 'var foo = true;',
parser: 'typescript-eslint-parser',
parser: '@typescript-eslint/parser',
Copy link
Collaborator

Choose a reason for hiding this comment

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

can you move parser and parserOptions to

construleTester=newRuleTester();
construleTester=newRuleTester({parserOptions:{ecmaVersion:6,sourceType:'module',ecmaFeatures:{}},parser:'@typescript-eslint/parser',project:'./tests/tsconfig.json'});

// their work around exposing the parser. They may require that there be a project config field in
// the eslint config, in which case we should check and/or report that here appropriately.
throw new Error(
'This rule requires you to use `eslint-plugin-typescript/parser`.'
'This rule requires you to use `@typescript-eslint/eslint-plugin/parser`.'
Copy link
Collaborator

@armano2armano2Jan 19, 2019
edited
Loading

Choose a reason for hiding this comment

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

Suggested change
'This rule requires you to use `@typescript-eslint/eslint-plugin/parser`.'
`You must provide a value for the "parserOptions.project" property for@typescript-eslint/parser`

its same message as in plugin-tslint

@JamesHenryJamesHenry merged commit132c078 intomasterJan 19, 2019
@JamesHenryJamesHenry deleted the names branchJanuary 19, 2019 23:18
@JamesHenry
Copy link
MemberAuthor

@armano2 Thanks I've noted down your points, adding them to my follow up PR - lots of tweaks to make yet anyway and I don't want anyone starting any WIP without the big reorg/renaming

armano2 reacted with thumbs up emoji

@github-actionsgithub-actionsbot locked asresolvedand limited conversation to collaboratorsApr 21, 2020
Sign up for freeto subscribe to this conversation on GitHub. Already have an account?Sign in.
Reviewers

@armano2armano2armano2 requested changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

2 participants
@JamesHenry@armano2

[8]ページ先頭

©2009-2025 Movatter.jp