Skip to content
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

tools: enforce errors to not be documented in legacy section #55218

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

Conversation

RedYetiDev
Copy link
Member

@RedYetiDev RedYetiDev commented Oct 1, 2024

This PR updates the lint rule to enforce that errors are in the right category. That is, errors that exist are not placed under the deprecated cateogory.

@nodejs-github-bot nodejs-github-bot added doc Issues and PRs related to the documentations. errors Issues and PRs related to JavaScript errors originated in Node.js core. labels Oct 1, 2024
@RedYetiDev RedYetiDev added the tools Issues and PRs related to the tools directory. label Oct 1, 2024
Copy link

codecov bot commented Oct 1, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 88.40%. Comparing base (1d5ed72) to head (dc1320c).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main   #55218      +/-   ##
==========================================
- Coverage   88.41%   88.40%   -0.02%     
==========================================
  Files         652      652              
  Lines      186572   186572              
  Branches    36045    36041       -4     
==========================================
- Hits       164957   164938      -19     
- Misses      14899    14905       +6     
- Partials     6716     6729      +13     

see 31 files with indirect coverage changes

doc/api/errors.md Outdated Show resolved Hide resolved
@aduh95 aduh95 changed the title doc: put errors in right location tools: enforce errors to not be documented in legacy section Oct 2, 2024
@RedYetiDev RedYetiDev closed this Oct 2, 2024
@RedYetiDev
Copy link
Member Author

RedYetiDev commented Oct 2, 2024

ack! That's not what I meant to do. --force will be the end of me...

I'll reopen in a moment.

@RedYetiDev RedYetiDev reopened this Oct 2, 2024
@RedYetiDev RedYetiDev requested a review from aduh95 October 2, 2024 16:24
doc/api/errors.md Outdated Show resolved Hide resolved
@aduh95
Copy link
Contributor

aduh95 commented Oct 2, 2024

Can you please rebase?

Co-authored-by: Antoine du Hamel <[email protected]>
@RedYetiDev RedYetiDev added the commit-queue-squash Add this label to instruct the Commit Queue to squash all the PR commits into the first one. label Oct 2, 2024
@aduh95 aduh95 added author ready PRs that have at least one approval, no pending requests for changes, and a CI started. request-ci Add this label to start a Jenkins CI on a PR. labels Oct 2, 2024
@github-actions github-actions bot removed the request-ci Add this label to start a Jenkins CI on a PR. label Oct 2, 2024
@nodejs-github-bot
Copy link
Collaborator

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
author ready PRs that have at least one approval, no pending requests for changes, and a CI started. commit-queue-squash Add this label to instruct the Commit Queue to squash all the PR commits into the first one. doc Issues and PRs related to the documentations. errors Issues and PRs related to JavaScript errors originated in Node.js core. tools Issues and PRs related to the tools directory.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants