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

docs: fix up config links#11254

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

Open
kirkwaiblinger wants to merge4 commits intotypescript-eslint:main
base:main
Choose a base branch
Loading
fromkirkwaiblinger:fix-up-config-links

Conversation

kirkwaiblinger
Copy link
Member

PR Checklist

Overview

Affectshttps://typescript-eslint.io/users/configs

Addresses 2 issues.

  1. https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/eslint-plugin/src/configs/eslintrc/eslint-recommended.ts is a bad link to use foreslint-recommended. It's technically true but doesn't show its contents. So, I've changed it tohttps://github.com/typescript-eslint/typescript-eslint/blob/main/packages/eslint-plugin/src/configs/eslint-recommended-raw.ts

  2. The wording "Seeconfigs/<config-name>.ts for the exact contents of this config" doesn't really work because those configs are now atconfigs/eslintrc/<config-name>.ts (with the exception of bullet point 1, which is atconfigs/eslint-recommended-raw.ts). Since puttingeslintrc and*-raw in the link text is IMO distracting, I've opted to change the wording to "Seethe source code for this config for the exact contents"... Not dead set on this solution, but I'd like to avoid putting the technically-falseconfigs/<config-name>.ts in the text.

@typescript-eslint
Copy link
Contributor

Thanks for the PR,@kirkwaiblinger!

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.

@netlifyNetlify
Copy link

netlifybot commentedMay 30, 2025
edited
Loading

Deploy Preview fortypescript-eslint ready!

NameLink
🔨 Latest commita39a32b
🔍 Latest deploy loghttps://app.netlify.com/projects/typescript-eslint/deploys/683a079a8c844c00082fc5f0
😎 Deploy Previewhttps://deploy-preview-11254--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: 93 (🔴 down 4 from production)
Accessibility: 100 (no change from production)
Best Practices: 100 (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 project configuration.

@nx-cloudNx Cloud
Copy link

nx-cloudbot commentedMay 30, 2025
edited
Loading

View yourCI Pipeline Execution ↗ for commita39a32b.

CommandStatusDurationResult
nx run-many -t typecheck✅ Succeeded1m 54sView ↗
nx run-many -t lint✅ Succeeded14sView ↗
nx test eslint-plugin --coverage=false✅ Succeeded<1sView ↗
nx run generate-configs✅ Succeeded8sView ↗
nx run types:build✅ Succeeded1sView ↗
nx test eslint-plugin-internal --coverage=false✅ Succeeded<1sView ↗
nx run integration-tests:test✅ Succeeded<1sView ↗
nx test typescript-estree --coverage=false✅ Succeeded<1sView ↗
Additional runs (27)✅ Succeeded...View ↗

☁️Nx Cloud last updated this comment at2025-05-30 19:41:19 UTC

bradzacher
bradzacher previously approved these changesMay 30, 2025
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.

+1 in general, but with an accessibility note

kirkwaiblinger reacted with thumbs up emoji
@@ -144,7 +144,7 @@ module.exports = {
</TabItem>
</Tabs>

See [`configs/recommended.ts`](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/eslint-plugin/src/configs/eslintrc/recommended.ts) for the exact contents of this config.
See [the source code for this config](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/eslint-plugin/src/configs/eslintrc/recommended.ts) for the exact contents.

Choose a reason for hiding this comment

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

https://www.w3.org/WAI/WCAG21/Understanding/link-purpose-in-context.html - the problem with having the same text on all links is they can't be disambiguated from just that text. Maybe...

Suggested change
See[the source code forthis config](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/eslint-plugin/src/configs/eslintrc/recommended.ts) for the exact contents.
See[the source code forthe`recommended` config](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/eslint-plugin/src/configs/eslintrc/recommended.ts) for the exact contents.

would be a good fix?

kirkwaiblinger reacted with thumbs up emoji
Copy link
MemberAuthor

Choose a reason for hiding this comment

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

Yes, agreed that that's better. Thanks for the suggestion!

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@bradzacherbradzacherbradzacher left review comments

@JoshuaKGoldbergJoshuaKGoldbergAwaiting requested review from JoshuaKGoldberg

Requested changes must be addressed to merge this pull request.

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

Successfully merging this pull request may close these issues.

3 participants
@kirkwaiblinger@JoshuaKGoldberg@bradzacher

[8]ページ先頭

©2009-2025 Movatter.jp