History

Orkuncakilkaya b839304f91 fix(cli): scaffold a project that compiles, and validate flags `ludic new my-game` wrote `program My-Game`, so the first thing anyone did with a new project — run it — failed with `expected '{', got '-'`. The project name is a directory name and the identifier is Ludic source, and they do not accept the same characters: names are now folded into a valid identifier (my-game -> MyGame, 2048 -> Game2048, a.b.c -> ABC) and a name that cannot be a directory or a package is refused with the rule instead of being mangled into one. An audit of every command's flags turned up more of the same shape, all fixed: - build/run ignored unknown options, so `--headles` silently produced a windowed binary, and `-o` with no path was silently dropped. - `ludic fmt` printed the formatted text to stdout while its help said "in place", so it appeared to do nothing. It writes now, with --check for the report-only case a hook wants. - `ludic test nosuch.ludic` deferred the error to the compiler. - build-lib's failure messages ran `{tmp_dir()}` through the shell literally — an interpolation written inside a non-interpolating string — and its argument guess matched package.lock.ludic, then tried to compile the lockfile. - Several messages still identified the tool as `x`. `ludic-dev test` now scaffolds under four awkward names, builds and tests each, and asserts a space-bearing name is refused — the case that shipped broken. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-05 23:27:16 +03:00
..
cli-audit.md	fix(cli): scaffold a project that compiles, and validate flags	2026-09-05 23:27:16 +03:00
README.md	refactor(cli)!: split the contributor tool out of the ludic CLI	2026-09-05 23:15:12 +03:00

Orkuncakilkaya b839304f91 fix(cli): scaffold a project that compiles, and validate flags

`ludic new my-game` wrote `program My-Game`, so the first thing anyone did with
a new project — run it — failed with `expected '{', got '-'`. The project name
is a directory name and the identifier is Ludic source, and they do not accept
the same characters: names are now folded into a valid identifier (my-game ->
MyGame, 2048 -> Game2048, a.b.c -> ABC) and a name that cannot be a directory or
a package is refused with the rule instead of being mangled into one.

An audit of every command's flags turned up more of the same shape, all fixed:

- build/run ignored unknown options, so `--headles` silently produced a windowed
  binary, and `-o` with no path was silently dropped.
- `ludic fmt` printed the formatted text to stdout while its help said "in
  place", so it appeared to do nothing. It writes now, with --check for the
  report-only case a hook wants.
- `ludic test nosuch.ludic` deferred the error to the compiler.
- build-lib's failure messages ran `{tmp_dir()}` through the shell literally —
  an interpolation written inside a non-interpolating string — and its argument
  guess matched package.lock.ludic, then tried to compile the lockfile.
- Several messages still identified the tool as `x`.

`ludic-dev test` now scaffolds under four awkward names, builds and tests each,
and asserts a space-bearing name is refused — the case that shipped broken.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

2026-09-05 23:27:16 +03:00

cli-audit.md

fix(cli): scaffold a project that compiles, and validate flags

2026-09-05 23:27:16 +03:00

README.md

refactor(cli)!: split the contributor tool out of the ludic CLI

2026-09-05 23:15:12 +03:00

README.md

Changesets

A changeset is one small Markdown file describing a single user-facing change, dropped in this directory. ludic-dev release consumes every changeset here into a new CHANGELOG.md section, bumps VERSION, and deletes the consumed files.

Format

bump: minor
type: feat
One or more lines describing the change, in the past-agnostic imperative used in
the changelog. Markdown is fine.

bump: — major, minor, or patch (SemVer). The release version is bumped by the highest level among the pending changesets (unless ludic-dev release <level> overrides it).
type: — the Conventional Commit type (feat, fix, perf, docs, …). It decides which group the change lands in: feat → Features, fix → Fixes, perf → Performance, and so on, in that order. A type with no known heading gets one named after itself.

Writing the body

The body is markdown and reaches the changelog as markdown: it becomes one list item, with continuation lines indented to stay inside it. Nested bullets, blank lines between paragraphs and inline code all survive.

bump: minor
type: feat
**Tiled map support** — load and draw Tiled maps.

- **TMX/TSX** — the XML formats, decoded to the same intermediate as JSON.
- **Collision** — the `collision` layer projects onto the engine tilemap.

Lead with the thing that changed, not with the mechanism. A reader scanning the release should be able to stop after your first clause.

Adding one

Create a file with a short, unique name, e.g. changes/regex-namespace.md. Any filename works except this README.md, which the release step always skips.

Preview how the next release will read before cutting it — this writes nothing:

ludic-dev release --dry-run