Skip to content

Conversation

@araujogui
Copy link
Member

@araujogui araujogui requested a review from a team as a code owner January 27, 2026 15:08
Copilot AI review requested due to automatic review settings January 27, 2026 15:08
@vercel
Copy link

vercel bot commented Jan 27, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
api-docs-tooling Ready Ready Preview Jan 27, 2026 4:14pm

Request Review

@codecov
Copy link

codecov bot commented Jan 27, 2026

Codecov Report

❌ Patch coverage is 0% with 5 lines in your changes missing coverage. Please review.
✅ Project coverage is 80.66%. Comparing base (baa1847) to head (c360a62).
✅ All tests successful. No failed tests found.

Files with missing lines Patch % Lines
src/generators/legacy-json-all/index.mjs 0.00% 4 Missing ⚠️
src/generators/legacy-json/index.mjs 0.00% 1 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #570      +/-   ##
==========================================
- Coverage   80.68%   80.66%   -0.02%     
==========================================
  Files         128      128              
  Lines       12389    12392       +3     
  Branches      887      887              
==========================================
  Hits         9996     9996              
- Misses       2390     2393       +3     
  Partials        3        3              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@github-actions
Copy link

github-actions bot commented Jan 27, 2026

orama-db Generator

File Base Head Diff
orama-db.json 8.02 MB 8.02 MB -1.86 KB (-0.02%)

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR attempts to fix test cases run by Node.js's test/doctool/test-doc-api-json.mjs by modifying the legacy JSON generator. The changes aim to adjust the JSON output format to match expected test results.

Changes:

  • Removed the api field from the root module object initialization in buildSection.mjs
  • Added JSON formatting with 2-space indentation to the JSON.stringify call in index.mjs

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File Description
src/generators/legacy-json/utils/buildSection.mjs Removes the api field from rootModule initialization
src/generators/legacy-json/index.mjs Adds formatting parameters to JSON.stringify for 2-space indented output

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@araujogui araujogui marked this pull request as draft January 27, 2026 15:28
@araujogui araujogui marked this pull request as ready for review January 27, 2026 15:50
@araujogui araujogui requested a review from ovflowd January 27, 2026 15:50

await writeFile(out, JSON.stringify(section));
// eslint-disable-next-line no-unused-vars
const { api, ...content } = section;
Copy link
Member

Choose a reason for hiding this comment

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

Not sure I like destructuring this tbh. I think since this is an extra field we could simply update upstream tests and add it to the allowlist on the test within the branch :)

Copy link
Member

Choose a reason for hiding this comment

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

Feel free to make a patch and I can amend it on the doc-kit PR on nodejs/node

Copy link
Member Author

Choose a reason for hiding this comment

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

Oh ok!

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants