fix: CopyPageButton on docs + array body coercion in API Reference#2973
Merged
Ishavyas9 merged 1 commit intoMay 22, 2026
Merged
Conversation
… API Reference - CopyPageButton was missing on Support Docs pages because index.tsx (which takes precedence over index.js in Docusaurus) did not include it. - API Reference Try It modal and code examples were sending array-type request body fields as strings instead of JSON arrays, causing 400 errors. Added coerceBodyValue() utility that handles both JSON syntax and comma-separated input. Affects 16 endpoints across 5 APIs. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Ishavyas9
approved these changes
May 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
index.tsxoverridesindex.jsin Docusaurus, and the.tsxfile was missing the CopyPageButton component.job_ids,tags,device) as plain strings instead of JSON arrays, causing 400 errors from APIs. AddedcoerceBodyValue()utility that supports both JSON syntax (["a","b"]) and comma-separated input (a, b). 16 endpoints across 5 APIs affected (Selenium Automation, App Automation, User Management, Test Manager, Analytics/RCA). Also added placeholder hint on array fields in Try It modal.Test plan
t1, t2→ verify request sends["t1", "t2"]not"t1, t2"["t1", "t2"]→ verify same result[]for array fields by default🤖 Generated with Claude Code