You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 5996c95
Browse filesBrowse the repository at this point in the historyBrowse files
404 suggests stacks; --stale-days=N honoured; bot issue lookups see every open issue
- data payload gains stacks [{ id, title }] (schema and docs updated); the
404 page matches a mistyped /stack/<id>/ against them and falls back to
"See all stacks" (#249)
- staleDaysFrom reads --stale-days=N as well as --stale-days N (#250)
- links, reverify and thumbs workflows pass --limit 1000 to gh issue list,
so an older bot issue is found and updated, not duplicated (#248)
Closes#248Closes#249Closes#250
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LpkeXQPaUhxjgqdqnk6BrJ
Copy file name to clipboardExpand all lines: docs/data.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ The catalog is published as machine-readable files on every deploy. The metadata
8
8
9
9
| File | What it is |
10
10
| --- | --- |
11
-
|[`data.json`](https://tmhsdigital.github.io/Free-Game-Dev-Assets/data.json)| The whole catalog: every entry with its licence fields, plus categories, guides and counts |
11
+
|[`data.json`](https://tmhsdigital.github.io/Free-Game-Dev-Assets/data.json)| The whole catalog: every entry with its licence fields, plus categories, guides, stacks and counts |
12
12
|[`data.schema.json`](https://tmhsdigital.github.io/Free-Game-Dev-Assets/data.schema.json)| JSON Schema (draft 2020-12) for `data.json`. The build fails if `data.json` does not match it |
13
13
|[`catalog.csv`](https://tmhsdigital.github.io/Free-Game-Dev-Assets/catalog.csv)| One row per entry, for spreadsheets. Lists are joined with `; `|
14
14
|[`feed.xml`](https://tmhsdigital.github.io/Free-Game-Dev-Assets/feed.xml)| Atom feed of newly added sources |
@@ -47,7 +47,7 @@ Each entry in `data.json` has these fields. `catalog.csv` has the ones marked CS
47
47
|`attributionClass`, `licenseRank`|| Derived sort keys used by the site |
48
48
|`maintenance`, `engine_lock`, `ue_versions`, `limits`, `grid_dimensions`, `camera_perspective`, `hardware_tags`|| Present only where they apply; see [the site README](../site/README.md)|
49
49
50
-
Top-level keys are `generatedAt`, `version`, `site`, `categories`, `guides`, `featured`, `stats` (counts of total, active, needs-review, deprecated and commercial entries), `filters` (`licenseFamilies` and `formatGroups`, the labels and groups behind the site's filters) and `entries`.
50
+
Top-level keys are `generatedAt`, `version`, `site`, `categories`, `guides`, `stacks` (id and title of each starter stack), `featured`, `stats` (counts of total, active, needs-review, deprecated and commercial entries), `filters` (`licenseFamilies` and `formatGroups`, the labels and groups behind the site's filters) and `entries`.
51
51
52
52
Field names are stable, and [`data.schema.json`](https://tmhsdigital.github.io/Free-Game-Dev-Assets/data.schema.json) states them as a JSON Schema the build enforces, so a field cannot be renamed or retyped without the schema changing too. New optional fields may appear, so ignore keys you do not know rather than failing on them (the schema itself rejects unknown keys, which is how the build catches drift).
eq("stale-days=N value (#250)",staleDaysFrom(["node","x","--stale-days=30"]).days,30);
1027
+
has("stale-days= empty is an error",staleDaysFrom(["node","x","--stale-days="]).error,"whole number");
1026
1028
has("stale-days as the last argument is an error",staleDaysFrom(["node","x","--stale-days"]).error,"got nothing");
1027
1029
has("stale-days followed by another flag is an error",staleDaysFrom(["node","x","--stale-days","--report"]).error,"--stale-days needs a whole number");
1028
1030
has("stale-days non-number is an error",staleDaysFrom(["node","x","--stale-days","soon"]).error,'"soon"');
0 commit comments