Skip to content

fix: bare rababa (no config) raises MapLogicError, not ArgumentError - #850

Merged
ronaldtse merged 1 commit into
mainfrom
g11-rababa
Nov 14, 2026
Merged

ronaldtse merged 1 commit into
mainfrom
g11-rababa

Conversation

@ronaldtse

Copy link
Copy Markdown
Contributor

WO18 parity audit gap G11: rababa without config: parses in all four runtimes (the grammar's kwargs are optional), but ruby executed it into a Ruby-level ArgumentError: missing keyword: :config - accidental, not a named map-logic failure. ts/py raise their named provisioning errors; rs rejects at load.

Ruby now raises Interscript::MapLogicError, "rababa requires config:". rababa_reverse already defaulted config: and is unchanged. TDD: spec red (ArgumentError) then green; full rake 422 examples / 0 failures / 11 pending.

The grammar's funcall kwargs are optional, so a bare `rababa`
directive parses everywhere - and ruby executed it into "ArgumentError:
missing keyword: :config" (audit G11, probe funcall-rababa-bare). ts/py
raise their named provisioning errors and rs rejects at load; ruby now
fails named too: MapLogicError "rababa requires config:". rababa_reverse
already defaulted config and is unchanged.

TDD: rspec red (ArgumentError) -> green; full rake 422 examples, 0
failures, 11 pending (baseline shape).
@ronaldtse
ronaldtse merged commit 529665a into main Nov 14, 2026
13 checks passed
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