Skip to content

fix: split non-parameter items from typed lists in signature tables - #1023

Open
btea wants to merge 3 commits into
nodejs:mainfrom
btea:fix/typed-list-non-parameter-items
Open

fix: split non-parameter items from typed lists in signature tables#1023
btea wants to merge 3 commits into
nodejs:mainfrom
btea:fix/typed-list-non-parameter-items

Conversation

@btea

@btea btea commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

Description

When a loose markdown list in API docs starts with typed parameters (e.g. actual, expected, Returns) but also contains plain prose bullets (e.g. algorithm complexity notes in util.diff), the entire list was treated as a parameter signature table. The non-parameter items had no name or type, causing them to render as empty sections.

Split the list at the first non-parameter item: typed items become the FunctionSignature table, and remaining items render as regular markdown.

Affected pages: util, fs, quic (31 mixed lists across 4 files).

image

Validation

Related Issues

Check List

  • I have read the Contributing Guidelines and made commit messages that follow the guideline.
  • I have run node --run test and all tests passed.
  • I have check code formatting with node --run format:check & node --run lint.
  • I've covered new added functionality with unit tests if necessary.

When a loose markdown list in API docs starts with typed parameters
(e.g. `actual`, `expected`, `Returns`) but also contains plain prose
bullets (e.g. algorithm complexity notes in `util.diff`), the entire
list was treated as a parameter signature table. The non-parameter
items had no name or type, causing them to render as empty sections.

Split the list at the first non-parameter item: typed items become the
FunctionSignature table, and remaining items render as regular markdown.

Affected pages: util, fs, quic (31 mixed lists across 4 files).
@btea
btea requested a review from a team as a code owner August 11, 2026 04:17
@vercel

vercel Bot commented Aug 11, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated (UTC)
api-docs-tooling Ready Ready Preview Aug 11, 2026 10:22pm

Request Review

@codecov

codecov Bot commented Aug 11, 2026

Copy link
Copy Markdown

Codecov Report

❌ Patch coverage is 81.06061% with 25 lines in your changes missing coverage. Please review.
✅ Project coverage is 89.37%. Comparing base (f46a0bd) to head (23c7d8f).

Files with missing lines Patch % Lines
packages/react/src/jsx-ast/utils/buildContent.mjs 7.40% 25 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1023      +/-   ##
==========================================
- Coverage   89.43%   89.37%   -0.07%     
==========================================
  Files         203      203              
  Lines       18871    18986     +115     
  Branches     1763     1769       +6     
==========================================
+ Hits        16878    16968      +90     
- Misses       1986     2011      +25     
  Partials        7        7              

☔ View full report in Codecov by Harness.
📢 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.

Comment thread packages/core/src/utils/queries/utils.mjs
Comment thread .changeset/fix-typed-list-split.md Outdated
Co-authored-by: Aviv Keller <me@aviv.sh>
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.

3 participants