Conversation
|
🕵
|
Member
Author
|
🕵 Consolidated into #350 so the translation and generated API locale work remains in the existing pull request. |
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.
Generated Cloud and ClickStack OpenAPI operation pages bypassed the normal localized content route and explicitly disabled the language picker. Emit locale-prefixed operation routes in translation builds, expose all configured languages from English API pages, and render the English operation with the locale-specific untranslated-page notice at localized URLs. Exclude these generated routes from the ordinary locale catch-all to prevent collisions.
Validated with
pnpm run typecheck, a focused English build, and a focused Spanish translations build. The built Spanish artifact contains the localized API route, language alternatives, and translated fallback notice.Changelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes into CHANGELOG.md):
Show all documentation languages on generated API reference pages and provide working localized fallback routes.