chore(platforms): sync the catalogue snapshot with production - #1221
Merged
Merged
Conversation
…id and docker-extension instructions
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.
Follow-up to #1203 now that graphql-api#209 is deployed to production.
The committed snapshot was built offline from the seed before the API shipped. Regenerating it against the live catalogue (the real
platformTypes+platformInstallationsresponse from prod, run through the generator's own write path) shows types and routes identical and exactly two field differences:instructionson theandroidanddocker-extensionrows, added on the API side after the snapshot was cut.android: "Install the Remote.It ScreenView app from the Play Store, open it, and enter this code to register the device."docker-extension: "Install the Remote.It Jumpbox extension in Docker Desktop, open it, and enter this code to register."Both are translated into ja/de/es in the
platformsnamespace rather than left empty.No visible desktop change: both pages keep local JSX instructions, which win over the catalogue per the merge rule. The MCP
create_registration_codetool does return these strings forcodeplatforms, and the snapshot's contract is thatplatforms:checkpasses against production — it now does.Verification:
npm run platforms:checkagainst the live response reports up to date;i18n:checkpasses (4 locales, 3 namespaces); typecheck clean.