fix(docs): preserve items response fields - #6587

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

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview	Aug 12, 2026 2:43am

PR Summary

Low Risk
Docs-only bug fix in the generator and regenerated markdown. No runtime product behavior changes.

Overview
Fixes the docs generator so response fields named items are no longer dropped when they collide with JSON Schema array items keywords.

parsePropertiesContent and parseConstProperties now keep items as a real output field, and nested schema lookups use top-level matching when the field itself is named items. Adds regression tests and regenerates affected integration docs (Gong, Google Forms, 1Password, SAP Concur, SharePoint, Stripe) so those fields appear in the output tables.

^{Reviewed by Cursor Bugbot for commit 9236a2d. Bugbot is set up for automated code reviews on this repo. Configure here.}

Greptile Summary

The PR fixes documentation schema parsing so response properties named items are preserved without being confused with structural array-item schemas.

• Adds depth-aware matching for structural properties and items keywords.
• Adds regression coverage for inline, constant-backed, and constant-property output definitions.
• Regenerates affected integration documentation to include previously omitted response fields.

Confidence Score: 5/5

The PR appears safe to merge with no actionable defects identified.

The parser now distinguishes response fields named items from structural schema keywords, and the added regression cases cover the changed inline and constant-resolution paths.

_{Reviews (1): Last reviewed commit: "fix(docs): preserve items response field..." | Re-trigger Greptile}