andrew/libakgl
1
0
Fork 0
Code Issues 67 Pull Requests Actions Packages Projects Releases Wiki Activity

util/assets/littleguy.json does not load #53

New Issue
Open
opened 2026-08-02 18:33:39 -04:00 by tachikoma · 0 comments
tachikoma commented 2026-08-02 18:33:39 -04:00
Collaborator
Copy Link

Source: TODO.md, "Found while writing the manual" -> "Defects with no prior entry", item 18 (at bbb7b8f)

The sample data for charviewer -- the one demo program the library ships --
uses the pre-0.5.0 unprefixed state names (ACTOR_STATE_ALIVE) and
velocity_x/velocity_y instead of speed_x/speed_y.

The current loader accepts neither, so the demo fails on its own sample data.

Cheap to fix and disproportionately visible: it is the first thing anyone runs.
Worth a smoke test that loads it, so the demo's fixture cannot rot again the next
time a JSON key is renamed.

Files: util/assets/littleguy.json, util/charviewer.c

Filed by Tachikoma (Claude Code, Opus 5, 1M context)

**Source:** TODO.md, "Found while writing the manual" -> "Defects with no prior entry", item 18 (at bbb7b8f) The sample data for `charviewer` -- **the one demo program the library ships** -- uses the pre-0.5.0 unprefixed state names (`ACTOR_STATE_ALIVE`) and `velocity_x`/`velocity_y` instead of `speed_x`/`speed_y`. The current loader accepts neither, so the demo fails on its own sample data. Cheap to fix and disproportionately visible: it is the first thing anyone runs. Worth a smoke test that loads it, so the demo's fixture cannot rot again the next time a JSON key is renamed. **Files:** `util/assets/littleguy.json`, `util/charviewer.c` --- Filed by Tachikoma (Claude Code, Opus 5, 1M context)
tachikoma added this to the 0.9.x milestone 2026-08-02 18:33:39 -04:00
tachikoma added the defectblast-radius:medium labels 2026-08-02 18:33:39 -04:00
tachikoma added the status::grooming label 2026-08-02 18:49:24 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
abi-break
Cannot land without a soname bump
 api-gap
A caller cannot express something
 blast-radius:high
Ordering: highest blast radius
 blast-radius:low
Ordering: lowest blast radius
 blast-radius:medium
Ordering: middling blast radius
 defect
Wrong behaviour reachable from the public API
 design-decision
Needs a decision written down before code
 docs
Header comments, manual, AGENTS.md
 hygiene
Style, dead code, consistency
 packaging
Build, install, pkg-config, CMake config
 performance
Has a number in PERFORMANCE.md behind it
 status::blocked
Waiting on something else -- a decision, a dependency, or another issue
 status::grooming
Not yet worked out: scope, approach or priority still being settled
 status::ready
Understood well enough to start: scope and approach are settled
 test-coverage
A gap in the suites, not a defect
No Label blast-radius:medium defect status::grooming
Milestone
No items
No Milestone 0.9.x
Projects
Clear projects
No project
Assignees
Clear assignees
tachikoma andrew
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: andrew/libakgl#53
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?