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

fix: subject fixed failure to propgate extension rules present in standard #583

Closed

Conversation

6XGate
Copy link

@6XGate 6XGate commented May 28, 2021

What is the purpose of this pull request? (put an "X" next to item)

[ ] Documentation update
[x] Bug fix
[ ] New feature
[ ] Other, please explain:

What changes did you make? (Give an overview)

Ensured that all @typescript-eslint rules are propagated if they appear in the Standard JS configuration.

Which issue (if any) does this pull request address?

#582 Some upstream standard rules are not properly propagated to their @typescript-eslint version

Is there anything you'd like reviewers to focus on?

@welcome
Copy link

welcome bot commented May 28, 2021

🙌 Thanks for opening this pull request! You're awesome.

@6XGate 6XGate force-pushed the feature/propagate-all-extension-rules branch from 8f9035f to 75a9d51 Compare May 29, 2021 00:45
@6XGate 6XGate changed the title Feature/propagate all extension rules fix: subject fixed failure to propgate extension rules present in standard May 29, 2021
@theoludwig theoludwig requested a review from mightyiam June 13, 2021 20:55
Copy link
Contributor

@theoludwig theoludwig left a comment

Choose a reason for hiding this comment

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

Looks good to me! 👍
But I don't know much of this codebase, so I'll let @mightyiam decide to approve and merge this PR.

Thanks for your contribution! @6XGate

package.json Outdated
Comment on lines 58 to 75
"@typescript-eslint/parser": "^4.0.0",
"@typescript-eslint/parser": "^4.15.0",
"eslint-config-standard": "^16.0.0"
},
"peerDependencies": {
"@typescript-eslint/eslint-plugin": ">=4.15.0",
"eslint": ">=7.12.1",
"eslint-plugin-import": ">=2.22.1",
"eslint-plugin-node": ">=11.1.0",
"eslint-plugin-promise": ">=4.2.1",
"typescript": ">=3.9",
"@typescript-eslint/eslint-plugin": ">=4.0.1"
"typescript": ">=3.9"
},
"devDependencies": {
"@commitlint/cli": "12.1.4",
"@commitlint/config-conventional": "12.1.4",
"@commitlint/travis-cli": "12.1.4",
"@types/eslint": "7.2.13",
"@types/node": "14.17.3",
"@typescript-eslint/eslint-plugin": "4.0.1",
"@typescript-eslint/eslint-plugin": "4.15.0",
Copy link
Owner

Choose a reason for hiding this comment

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

I'd like dependency upgrades in a separate PR, even if they are necessary for this one, please.

Copy link
Contributor

Choose a reason for hiding this comment

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

PR available there: #592

Copy link
Author

Choose a reason for hiding this comment

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

#592 failed checks due to one of the dependency constraints changing in standard that this code base originally take into account. I fixed it here, so hope that won't be an issue.

Copy link
Contributor

Choose a reason for hiding this comment

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

Actually, it will be fixed with #590.

@rostislav-simonik
Copy link
Collaborator

@6XGate sorry for not reviewing your PR until now, if we review it, will you proceed with it?

@6XGate
Copy link
Author

6XGate commented Jul 15, 2022

proceed with it? I'm not sure what you mean by that.
It likely will need to corrections due to recently landed PRs.
It was meant to better keep in sync with standard by sync all know (at the time) shared/replaced plain ESLint rules with their TypeScript counter part

@mightyiam
Copy link
Owner

@6XGate yes. If we review it will you follow through with it with it? It's been a while. That's why we ask.

@6XGate
Copy link
Author

6XGate commented Jul 21, 2022

Sure, I'll give a try at it again soon.

@mightyiam
Copy link
Owner

I'm happy to hear that, @6XGate . But we haven't reviewed it yet, so don't spend time yet. Now that I know you're willing to go through with it, we'll review it for you. Not before August though.

mightyiam added a commit that referenced this pull request Sep 13, 2022
BREAKING CHANGE: add rules from @typescript-eslint: no-extra-parens,
no-loss-of-precision, object-curly-spacing, space-before-blocks,
comma-dangle.

Closes #582, closes #583.

Co-authored-by: Rostislav Simonik <[email protected]>
mightyiam added a commit that referenced this pull request Sep 13, 2022
BREAKING CHANGE: add rules from @typescript-eslint: no-extra-parens,
no-loss-of-precision, object-curly-spacing, space-before-blocks,
comma-dangle.

Closes #582, closes #583.

Co-authored-by: Rostislav Simonik <[email protected]>
@mightyiam mightyiam closed this in 1e8764d Sep 13, 2022
eslint-config-love-release-bot bot pushed a commit that referenced this pull request Sep 13, 2022
## [23.0.0](v22.0.0...v23.0.0) (2022-09-13)

### ⚠ BREAKING CHANGES

* add rules from @typescript-eslint: no-extra-parens,
no-loss-of-precision, object-curly-spacing, space-before-blocks,
comma-dangle.

### Features

* use all typescript-eslint equivalents ([1e8764d](1e8764d)), closes [#582](#582) [#583](#583)

### CI

* continuous delivery ([971c680](971c680)), closes [#840](#840)

### Build system / dependencies

* renovate automergeMinor github actions ([02dde9d](02dde9d)), closes [#910](#910)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants