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 broken link in getting started page details section#8463

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
bradzacher merged 2 commits intotypescript-eslint:mainfromsalitha-pathi:patch-1
Feb 14, 2024

Conversation

salitha-pathi
Copy link
Contributor

@salitha-pathisalitha-pathi commentedFeb 14, 2024
edited
Loading

PR Checklist

Overview

Hey! 👋

I noticed a broken link in the "Getting Started" page, specifically in the "Details" section under the recommended configurations link. It was pointing to localhost instead of the correct public domain.

I've updated the link to direct users to the correct destination.

As far as I can tell, there are no open issues related to this, and it's likely that no one has noticed the broken link yet.

This PR resolves the issue and ensures a smoother experience for users navigating the documentation.

Thanks for reviewing! 🚀

Corrects a broken link in the recommended configurations. Previously pointing to localhost, the link has been updated to the correct public host
@typescript-eslint
Copy link
Contributor

Thanks for the PR,@salitha-pathi!

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 commentedFeb 14, 2024
edited
Loading

Deploy Preview fortypescript-eslint ready!

NameLink
🔨 Latest commitc10fdc3
🔍 Latest deploy loghttps://app.netlify.com/sites/typescript-eslint/deploys/65cc69e00bc88b0008cf4f2e
😎 Deploy Previewhttps://deploy-preview-8463--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: 90 (🟢 up 2 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-cloudNx Cloud
Copy link

nx-cloudbot commentedFeb 14, 2024
edited
Loading

☁️ Nx Cloud Report

CI is running/has finished running commands for commitc10fdc3. 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 33 targets

Sent with 💌 fromNxCloud.

@codecovCodecov
Copy link

codecovbot commentedFeb 14, 2024
edited
Loading

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base(2b98ccd) 87.74% compared to head(e61ba4d) 86.94%.

❗ Current heade61ba4d differs from pull request most recent headc10fdc3. Consider uploading reports for the commitc10fdc3 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@##             main    #8463      +/-   ##==========================================- Coverage   87.74%   86.94%   -0.81%==========================================  Files         398      252     -146       Lines       13827    12251    -1576       Branches     4067     3861     -206     ==========================================- Hits        12133    10652    -1481+ Misses       1397     1332      -65+ Partials      297      267      -30
FlagCoverage Δ
unittest86.94% <ø> (-0.81%)⬇️

Flags with carried forward coverage won't be shown.Click here to find out more.

see 146 files with indirect coverage changes

Copy link
Member

@bradzacherbradzacher left a comment

Choose a reason for hiding this comment

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

Huh how did that get in there! Thanks!!

salitha-pathi reacted with heart emoji
@bradzacherbradzacher changed the titleDocs: Fix broken link in getting started page details sectiondocs: Fix broken link in getting started page details sectionFeb 14, 2024
@@ -72,7 +72,7 @@ The [`config`](./packages/TypeScript_ESLint.mdx) helper sets three parts of ESLi

- [Parser](https://eslint.org/docs/latest/use/configure/parser): set to [`@typescript-eslint/parser`](./packages/Parser.mdx) so ESLint knows how to parse the new pieces of TypeScript syntax.
- [Plugins](https://eslint.org/docs/latest/use/configure/plugins): set to [`@typescript-eslint/eslint-plugin`](./packages/ESLint_Plugin.mdx) to load [rules listed in our _Rules_ page](./Rules).
- [Rules](https://eslint.org/docs/latest/use/configure/rules): extends from our [recommended configuration](http://localhost:3000/linting/configs#recommended) to enable our most commonly useful lint rules.
- [Rules](https://eslint.org/docs/latest/use/configure/rules): extends from our [recommended configuration](https://typescript-eslint.io/linting/configs/#recommended) to enable our most commonly useful lint rules.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
-[Rules](https://eslint.org/docs/latest/use/configure/rules): extends from our[recommended configuration](https://typescript-eslint.io/linting/configs/#recommended) to enable our most commonly useful lint rules.
-[Rules](https://eslint.org/docs/latest/use/configure/rules): extends from our[recommended configuration](./linting/configs/#recommended) to enable our most commonly useful lint rules.

Let's update it to a relative path? This is a more flexible solution than a hard-coded URL. It will work correctly regardless of the domain name! For example, in Netlify Preview Deployments (preview deployment for this PR). What do you think?

bradzacher reacted with thumbs up emoji
Copy link
Member

@bradzacherbradzacher left a comment

Choose a reason for hiding this comment

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

(can't edit the PR myself)

@@ -72,7 +72,7 @@ The [`config`](./packages/TypeScript_ESLint.mdx) helper sets three parts of ESLi

- [Parser](https://eslint.org/docs/latest/use/configure/parser): set to [`@typescript-eslint/parser`](./packages/Parser.mdx) so ESLint knows how to parse the new pieces of TypeScript syntax.
- [Plugins](https://eslint.org/docs/latest/use/configure/plugins): set to [`@typescript-eslint/eslint-plugin`](./packages/ESLint_Plugin.mdx) to load [rules listed in our _Rules_ page](./Rules).
- [Rules](https://eslint.org/docs/latest/use/configure/rules): extends from our [recommended configuration](http://localhost:3000/linting/configs#recommended) to enable our most commonly useful lint rules.
- [Rules](https://eslint.org/docs/latest/use/configure/rules): extends from our [recommended configuration](https://typescript-eslint.io/linting/configs/#recommended) to enable our most commonly useful lint rules.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
-[Rules](https://eslint.org/docs/latest/use/configure/rules): extends from our[recommended configuration](https://typescript-eslint.io/linting/configs/#recommended) to enable our most commonly useful lint rules.
-[Rules](https://eslint.org/docs/latest/use/configure/rules): extends from our[recommended configuration](./linting/configs/#recommended) to enable our most commonly useful lint rules.

Can you please use a relative link instead?

@bradzacherbradzacher changed the titledocs: Fix broken link in getting started page details sectiondocs: fix broken link in getting started page details sectionFeb 14, 2024
@bradzacherbradzacher merged commit6a875b4 intotypescript-eslint:mainFeb 14, 2024
yeonjuan pushed a commit to yeonjuan/typescript-eslint that referenced this pull requestFeb 18, 2024
@github-actionsgithub-actionsbot locked asresolvedand limited conversation to collaboratorsFeb 22, 2024
Sign up for freeto subscribe to this conversation on GitHub. Already have an account?Sign in.
Reviewers

@auvredauvredauvred requested changes

@bradzacherbradzacherbradzacher 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.

3 participants
@salitha-pathi@bradzacher@auvred

[8]ページ先頭

©2009-2025 Movatter.jp