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

feat(eslint-plugin): [no-restricted-imports] support import = require#7709

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

Conversation

@Josh-Cena
Copy link
Member

@Josh-CenaJosh-Cena commentedOct 1, 2023
edited
Loading

PR Checklist

Overview

@typescript-eslint
Copy link
Contributor

Thanks for the PR,@Josh-Cena!

typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community.

The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately.

Thanks again!


🙏Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently onhttps://opencollective.com/typescript-eslint.

@netlify
Copy link

netlifybot commentedOct 1, 2023
edited
Loading

Deploy Preview fortypescript-eslint ready!

NameLink
🔨 Latest commitf9befaf
🔍 Latest deploy loghttps://app.netlify.com/sites/typescript-eslint/deploys/652efcc1e4c1ef00085765fa
😎 Deploy Previewhttps://deploy-preview-7709--typescript-eslint.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 98 (🟢 up 3 from production)
Accessibility: 100 (no change from production)
Best Practices: 92 (no change from production)
SEO: 98 (no change from production)
PWA: 80 (no change from production)
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to yourNetlify site configuration.

@nx-cloud
Copy link

nx-cloudbot commentedOct 1, 2023
edited
Loading

☁️ Nx Cloud Report

CI is running/has finished running commands for commitf9befaf. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution


✅ Successfully ran 19 targets

Sent with 💌 fromNxCloud.

Copy link
Member

@JoshuaKGoldbergJoshuaKGoldberg left a comment

Choose a reason for hiding this comment

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

Swell, LGTM!

I think this is a breaking change and blocked on going into our next major release?

>See**https://typescript-eslint.io/rules/no-restricted-imports** for documentation.
This rule extends the base[`eslint/no-restricted-imports`](https://eslint.org/docs/rules/no-restricted-imports) rule.
This rule extends the base[`eslint/no-restricted-imports`](https://eslint.org/docs/rules/no-restricted-imports) rule. It adds support for the type import (`import type X from "..."`,`import { type X } from "..."`) and`import x = require("...")` syntaxes.

Choose a reason for hiding this comment

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

[Praise] Yes! I've started souring on extension docs that don't explicitly say what gets added.

specifier.importKind==='type',
))
!isAllowedTypeImportPath(importSource)&&
!isAllowedTypeImportPattern(importSource)

Choose a reason for hiding this comment

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

[Cleanup] Nit: there's a teeny bit of duplication with calling!isAllowedTypeImportPath(importSource) && !isAllowedTypeImportPattern(importSource). Maybe worth a helper function? It's only two places, so maybe not...

@JoshuaKGoldbergJoshuaKGoldberg added the breaking changeThis change will require a new major version to be released labelOct 8, 2023
@Josh-Cena
Copy link
MemberAuthor

Josh-Cena commentedOct 8, 2023
edited
Loading

I don't think this qualifies as a breaking change (if people really think so it can be behind an option). We usually don't automatically categorize "more errors" as breaking change, especially in the case where an error should be highly expected and the lack of one can only be explained as a bug/oversight.

@JoshuaKGoldberg
Copy link
Member

Yeah I think you're right. In theory, if a lot of devs still usedimport = require syntax, then I think this'd be more debatable. But it's not a super-used feature.

🚀 ship it!

@JoshuaKGoldbergJoshuaKGoldberg removed the breaking changeThis change will require a new major version to be released labelOct 17, 2023
@JoshuaKGoldbergJoshuaKGoldberg merged commit4c8edcf intotypescript-eslint:mainOct 18, 2023
@Josh-CenaJosh-Cena deleted the no-restricted-imports-check-require branchOctober 18, 2023 01:00
@github-actionsgithub-actionsbot locked asresolvedand limited conversation to collaboratorsOct 26, 2023
Sign up for freeto subscribe to this conversation on GitHub. Already have an account?Sign in.

Reviewers

@JoshuaKGoldbergJoshuaKGoldbergJoshuaKGoldberg approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

[no-restricted-imports] No way to use this rule withimport = require() syntax.

2 participants

@Josh-Cena@JoshuaKGoldberg

[8]ページ先頭

©2009-2025 Movatter.jp