[A/B — do not merge] Flatten Voice & Video nav to test version-tree 500 - #456
Closed
raj-dubey1 wants to merge 2 commits into
Closed
[A/B — do not merge] Flatten Voice & Video nav to test version-tree 500#456raj-dubey1 wants to merge 2 commits into
raj-dubey1 wants to merge 2 commits into
Conversation
Tests whether un-nesting versions from dropdowns stops the desktop version-switcher 500 (React insertBefore crash in Mintlify's bundle). Voice & Video Calling: the "SDK" tab's framework dropdowns (JavaScript, React Native, iOS, Android, Flutter), which nested `versions` inside a `dropdown` inside a `tab` (unsupported per Mintlify docs + discussion #2168), are converted to framework tabs carrying `versions` directly — Mintlify's supported "versions applied to a specific tab" pattern. Chat & Messaging is intentionally left nested as the control. No page paths changed; nav structure only. Not for merge. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
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
1 participant
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.
Purpose — A/B test only, NOT for merge (base retargeted to
mainso Mintlify builds a preview)Diagnostic experiment for the desktop version-switcher "Error 500" (React
insertBeforecrash inside Mintlify's bundle). Fires when the version tree opens on desktop (inline sidebar); mobile/tablet drawer is unaffected.Hypothesis
Crash is triggered by our unsupported nesting
tab → dropdowns → versions → groups. Mintlify requires one child-type per level, and versions-inside-dropdowns is an open, unsupported feature request (mintlify/discussions#2168). Onset ~2 days ago with no structural change on our side ⇒ Mintlify platform regression that stopped tolerating the nesting.What this branch changes — Voice & Video Calling only
SDKtab's framework dropdowns (JavaScript, React Native, iOS, Android, Flutter), which nestedversionsinside adropdown, are converted to framework tabs carryingversionsdirectly — Mintlify's supported "versions applied to a specific tab" pattern. No page paths changed.The A/B (both on this one preview)
calls/javascript/overviewopens the version switcher without a 500ui-kit/react/overview(left nested) still 500sIf that split holds, nesting is confirmed as the cause → roll
tab → versionsout site-wide.Note: diff vs
mainalso includes the prior invisible-char cleanup fromdocs/broken-version-tree-fix; the meaningful change is the V&V flatten. Not for merge.🤖 Generated with Claude Code