Skip to content

docs: rename "directive comments" to "comment directives" #11268

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

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

mrazauskas
Copy link
Contributor

@mrazauskas mrazauskas commented Jun 4, 2025

PR Checklist

Overview

This PR only renames "directive comments" into "comment directives" in documentation.

The wording is rather similar, indeed. It seems to me that "comment directives" is the preferred naming in the ecosystem:

@typescript-eslint
Copy link
Contributor

Thanks for the PR, @mrazauskas!

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 on https://opencollective.com/typescript-eslint.

Copy link

netlify bot commented Jun 4, 2025

Deploy Preview for typescript-eslint ready!

Name Link
🔨 Latest commit c694488
🔍 Latest deploy log https://app.netlify.com/projects/typescript-eslint/deploys/68428fb32f2cab000820a005
😎 Deploy Preview https://deploy-preview-11268--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 (🔴 down 1 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 your Netlify project configuration.

Copy link

nx-cloud bot commented Jun 4, 2025

View your CI Pipeline Execution ↗ for commit c694488.

Command Status Duration Result
nx test eslint-plugin --coverage=false ✅ Succeeded 4m 58s View ↗
nx run-many -t typecheck ✅ Succeeded 2m 7s View ↗
nx run-many -t lint ✅ Succeeded 11s View ↗
nx test eslint-plugin-internal --coverage=false ✅ Succeeded 7s View ↗
nx run generate-configs ✅ Succeeded 5s View ↗
nx test typescript-estree --coverage=false ✅ Succeeded <1s View ↗
nx run types:build ✅ Succeeded 1s View ↗
nx run integration-tests:test ✅ Succeeded <1s View ↗
Additional runs (27) ✅ Succeeded ... View ↗

☁️ Nx Cloud last updated this comment at 2025-06-06 07:01:21 UTC

@mrazauskas mrazauskas changed the title Update ban-ts-comment.mdx refactor: rename "directive comments" into "comment directives" Jun 4, 2025
@mrazauskas mrazauskas changed the title refactor: rename "directive comments" into "comment directives" docs: rename "directive comments" into "comment directives" Jun 4, 2025
@mrazauskas mrazauskas changed the title docs: rename "directive comments" into "comment directives" docs: rename "directive comments" to "comment directives" Jun 4, 2025
@kirkwaiblinger kirkwaiblinger added the 1 approval >=1 team member has approved this PR; we're now leaving it open for more reviews before we merge label Jun 6, 2025
Copy link
Member

@kirkwaiblinger kirkwaiblinger left a comment

Choose a reason for hiding this comment

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

This seems like a fine change to me 👍

Would you mind doing a search in the repo for any other instances where we use the term "directive comments" and replacing them as well? I see several code comments with this wording and we might as well switch them, too, I think

kirkwaiblinger
kirkwaiblinger previously approved these changes Jun 6, 2025
Copy link

codecov bot commented Jun 6, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.91%. Comparing base (0f5c59c) to head (c694488).

Additional details and impacted files
@@           Coverage Diff           @@
##             main   #11268   +/-   ##
=======================================
  Coverage   90.91%   90.91%           
=======================================
  Files         501      501           
  Lines       50869    50869           
  Branches     8382     8382           
=======================================
  Hits        46248    46248           
  Misses       4606     4606           
  Partials       15       15           
Flag Coverage Δ
unittest 90.91% <ø> (ø)

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

Files with missing lines Coverage Δ
packages/eslint-plugin/src/util/astUtils.ts 96.15% <ø> (ø)
.../scope-manager/src/variable/ESLintScopeVariable.ts 100.00% <ø> (ø)
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@mrazauskas
Copy link
Contributor Author

@kirkwaiblinger Thanks for feedback. I replaced all instances I could find.

Copy link
Member

@kirkwaiblinger kirkwaiblinger left a comment

Choose a reason for hiding this comment

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

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Development

Successfully merging this pull request may close these issues.

2 participants