Conversation
…itch Mintlify's language switcher navigates to the explicit href when set, instead of doing smart path prefix replacement. Removing href lets the switcher stay on the current page when switching languages. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…guage switch" This reverts commit b74b1b8.
…ions Mintlify's language switcher only preserves the current page when languages are the top-level navigation partition. Previously, versions were the top level with languages nested inside, causing the switcher to redirect to the introduction page instead of the same page in the target language. Also removes explicit href from language blocks and fixes ja having default=true incorrectly in the 3.2.x version config. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Mintlify generates page URL slugs from operationId. When operationIds differ between languages (e.g., en: sendChatMessage vs zh: sendBasicChatMessageCn), the language switcher can't find the equivalent page and falls back to the introduction page. This aligns all zh/ja operationIds to match en for endpoints that share the same HTTP method and path. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Mintlify uses OpenAPI tags to generate URL category paths (e.g., tag "Chat" → /chat/). When zh uses "对话消息" and ja uses "チャットメッセージ", the generated URLs differ from en's, breaking language switching. This aligns all zh/ja OpenAPI spec tags to match en, ensuring identical URL structures across languages. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Tags use English names for URL slug generation (consistent across languages) but x-displayName holds the translated names for display in the sidebar, so Chinese/Japanese users still see localized labels. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Mintlify generates API page URLs from the tag name + summary, both of
which are translated in zh/ja specs. This produces different URL slugs
(e.g., en: /chat/send-chat-message vs zh: /对话消息/发送对话消息),
making language switching impossible.
Instead of changing the visible content (tags, summaries), this adds
x-mint: { href: ... } to each endpoint in zh/ja specs, explicitly
setting the URL path to match en. All translated content (tags,
summaries, descriptions) is preserved as-is for readers.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…flicts Without the language prefix, zh/ja endpoints claimed the same absolute URL as en (e.g., /api-reference/chat/send-chat-message), causing ja content to appear on en pages. Now each language has its own prefixed href (e.g., /zh/api-reference/chat/send-chat-message), keeping content correctly scoped while enabling language switching. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…ignment) These changes are breaking and need careful coordination with the dev team before implementation. Only the navigation restructure (versions>languages → languages>versions) is kept for this PR. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Copilot wasn't able to review any files in this pull request.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
You can also share your feedback on Copilot code review. Take the survey.
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
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.
No description provided.