Add KSA to the status page game filters#2
Merged
Conversation
- Add a ksa GameConfig (status /status/netkan-ksa.json, netkan/history/metadata URLs at KSAModding/KSA-NetKAN and KSAModding/KSA-CKAN-meta on main) and append it to the games array that drives all filtering, fetching, and links. - Cover the new config in the game-config tests (URL builders plus the three-game array). - fetch-status.js: also fetch netkan-ksa.json; skip a status file that returns 404 (not published yet) with a warning so the other games still get fetched, keep any other failure fatal, and fail only when no file is published at all. - README: document the per-game status files; the KSA wget line is commented out until the NetKAN bot publishes the file.
Maximilian-Nesslauer
added
enhancement
averageksp
approved these changes
Jul 4, 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.
What
Adds Kitten Space Agency as a third game to the status page, mirroring how KSP2 was added (KSP-CKAN#25, adapted to the current React/TypeScript structure where everything is driven by the
gamesarray insrc/lib/game-config.ts):ksaGameConfig: status file/status/netkan-ksa.json, netkan/history links toKSAModding/KSA-NetKANand metadata links toKSAModding/KSA-CKAN-meta(both on branchmain). If the metadata repos are later transferred to KSP-CKAN, these URLs are the one place to flip.scripts/fetch-status.jsfetches the KSA file too. A status file that returns 404 (not published yet) is skipped with a warning so the other games still get fetched; any other failure (5xx, network, disk) stays fatal, and the run only fails outright when no file is published at all.No component changes were needed: filters, counts, table links, and fetching all derive from the
gamesarray.Not in scope / sequencing
The KSA filter stays empty until the NetKAN bot publishes
netkan-ksa.jsonto status.ksp-ckan.space, which needs the KSA inflator in NetKAN-Infra, which in turn needs KSA client support merged into upstream KSP-CKAN/CKAN. Merge order for the upstream PRs: client -> bot deploy -> this. See the tracking issue for details.Testing
game-configtests extended for the new config (URL builders, three-game array); full suite green: 164/164.tsc+vite buildclean.pnpm fetch:statusrun:netkan.jsonandnetkan-ksp2.jsonsaved,netkan-ksa.jsonskipped withSkipped netkan-ksa.json: not published (HTTP 404), exit code 0.Closes #1.