Skip to content

docs(sandbox): stop referencing a non-existent game.log API#57

Merged
Taure merged 1 commit into
mainfrom
docs/remove-game-log-phantom
Jun 29, 2026
Merged

docs(sandbox): stop referencing a non-existent game.log API#57
Taure merged 1 commit into
mainfrom
docs/remove-game-log-phantom

Conversation

@Taure

@Taure Taure commented Jun 29, 2026

Copy link
Copy Markdown
Contributor

The asobi-docs-auditor flagged a shared fiction across three surfaces: the sandbox docs direct users to an "asobi-side game.log API" for logging, but no such binding exists. print/eprint are stripped (asobi_lua_loader.erl L-1), and asobi_lua_api.erl registers no log path — there is currently no in-script logging facility.

This fixes the two asobi_lua surfaces:

  • guides/security-sandbox.md
  • the asobi_lua_loader.erl strip-list comment

(The matching site copy is fixed in widgrensit/asobi_site#67.)

Both now state the real situation: surface diagnostics through game state or broadcast events.

Whether to add a real game.log binding is a separate design decision (the sandbox deliberately strips stdout logging) — tracked separately, not done here.

Verification

rebar3 fmt --check, compile, xref, eunit (223/223), elp lint (no warnings on the loader). ex_doc warnings present are all pre-existing and unrelated.

print/eprint are stripped from the sandbox and no logging binding is
registered, so there is no in-script logging facility. The sandbox guide
and the loader comment both directed users to an asobi-side `game.log`
API that does not exist. State the actual situation instead: surface
diagnostics through game state or broadcast events.
@Taure Taure merged commit e56910e into main Jun 29, 2026
15 checks passed
@Taure Taure deleted the docs/remove-game-log-phantom branch June 29, 2026 18:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant