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: emphasize performance tradeoffs of typed linting#10730

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

JoshuaKGoldberg
Copy link
Member

PR Checklist

Overview

Adds almost no new content, instead emphasizing or reorganizing existing content:

  • Adds the suggested"which comes with performance tradeoffs" note to the auto-added cards on top of rules pages
  • Moves FAQs from/getting-started/typed-linting to the actual typed linting FAQs, promoting thePerformance heading to an h2

💖

@typescript-eslint
Copy link
Contributor

Thanks for the PR,@JoshuaKGoldberg!

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 commentedJan 28, 2025
edited
Loading

Deploy Preview fortypescript-eslint ready!

NameLink
🔨 Latest commita2cdccc
🔍 Latest deploy loghttps://app.netlify.com/sites/typescript-eslint/deploys/67a0dcf78af624000833b717
😎 Deploy Previewhttps://deploy-preview-10730--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 5 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 commentedJan 28, 2025
edited
Loading

View yourCI Pipeline Execution ↗ for commita2cdccc.

CommandStatusDurationResult
nx test utils✅ Succeeded<1sView ↗
nx test visitor-keys✅ Succeeded<1sView ↗
nx run types:build✅ Succeeded<1sView ↗
nx test type-utils✅ Succeeded<1sView ↗
nx run-many --target=build --exclude website --...✅ Succeeded4sView ↗
nx test utils --coverage=false✅ Succeeded<1sView ↗
nx test typescript-eslint✅ Succeeded<1sView ↗
nx run-many --target=clean✅ Succeeded13sView ↗
Additional runs (24)✅ Succeeded...View ↗

☁️Nx Cloud last updated this comment at2025-02-03 15:28:53 UTC

@JoshuaKGoldbergJoshuaKGoldberg requested review fromnzakas anda teamJanuary 29, 2025 20:39
JoshuaKGoldbergand others added3 commitsJanuary 31, 2025 08:35
Co-authored-by: Nicholas C. Zakas <nicholas@humanwhocodes.com>
@codecovCodecov
Copy link

codecovbot commentedJan 31, 2025
edited
Loading

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 87.27%. Comparing base(94e8098) to head(a2cdccc).
Report is 29 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@##             main   #10730   +/-   ##=======================================  Coverage   87.26%   87.27%           =======================================  Files         450      450             Lines       15712    15719    +7       Branches     4600     4601    +1     =======================================+ Hits        13711    13718    +7  Misses       1645     1645             Partials      356      356
FlagCoverage Δ
unittest87.27% <ø> (+<0.01%)⬆️

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

see 5 files with indirect coverage changes

This requires TypeScript to analyze your entire project instead of just the file being linted.

As a result, these rules are slower than traditional lint rules but are much more powerful.

To tap into TypeScript's additional powers, there are two small changes you need to make to your config file:

Choose a reason for hiding this comment

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

This sentence reads a little awkwardly now.... The "additional powers" is now kind of a dangling reference which used to point to the "...the awesome power...." in the formerly preceding sentence. The new "...much more powerful" doesn't set up quite the same parallelism. Any way to tweak this wording?

Copy link
MemberAuthor

Choose a reason for hiding this comment

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

Hmm yeah. I merged the first two groups together and switched the third to saying the more straightforward"enable type typed linting", WDYT?

@kirkwaiblingerkirkwaiblinger added the 1 approval>=1 team member has approved this PR; we're now leaving it open for more reviews before we merge labelFeb 10, 2025
@JoshuaKGoldbergJoshuaKGoldberg merged commite4994c5 intotypescript-eslint:mainFeb 10, 2025
65 checks passed
@github-actionsgithub-actionsbot locked asresolvedand limited conversation to collaboratorsFeb 18, 2025
Sign up for freeto subscribe to this conversation on GitHub. Already have an account?Sign in.
Reviewers

@nzakasnzakasnzakas left review comments

@kirkwaiblingerkirkwaiblingerkirkwaiblinger approved these changes

Assignees
No one assigned
Labels
1 approval>=1 team member has approved this PR; we're now leaving it open for more reviews before we merge
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Docs: Highlight performance issues with type-aware rules
3 participants
@JoshuaKGoldberg@nzakas@kirkwaiblinger

[8]ページ先頭

©2009-2025 Movatter.jp