All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
Entries for unreleased work are not written here directly. Each issue drops a
fragment in changelog.d/; the fragments are assembled
into a version section at release. See that README for the format and for when a
change warrants an entry at all.
[0.2.0] 2026-09-18
The residue wave after the first release. Riddler.Screens.validate_responses/3
and /4 give way to Riddler.Screens.validate_screen/3 and /4, which validate
against the same root the host resolved the screen with, and
Riddler.Screens.resolve_screen/3 answers its diagnostics alongside the screen.
A condition the root cannot decide is a finding rather than a silent pass, and a
button that declares it validates nothing is unaffected. A pattern the format
cannot compile is refused against the document before a visitor arrives, the
document schema is emitted as schemas/screen-document.schema.json and the
schemas ship in the package, and the emitted corpus header names no version, so
an emitted corpus is byte-identical across releases. A finding carries the
position in the source it refused, and a template the parser refuses without
saying where answers a finding rather than raising.
Added
- A finding carries
:position, the%{line: line, column: column}in the source it refused, so an editor can point at a refused template construct without parsing the message. A template refusal sets it, and adocument.invalid_templatefinding carries the position of the template refusal it wraps; every other finding leaves itnil. The message goes on naming the position in its own words wherever there is one. Riddler.Screens.validate_screen/3and/4validate against the root the host resolved with, so a required question acontextcondition showed the visitor is one the visitor can fail, where the removed pair resolved against an emptycontextand let the blank through.- The JSON schemas ship in the package, so a host that validates a document
against one at runtime can read it from
Application.app_dir(:riddler, "priv/schemas")instead of vendoring a copy.
Changed
- Breaking:
Riddler.Screens.resolve_screen/3answers{:ok, screen, diagnostics}where it answered{:ok, screen}; match on the three-element tuple and readmissing_variablesandundecidable_conditionsfromdiagnostics, which is the shaperesolve/2already carries on a resolved document, narrowed to the one screen. A caller that only wants the screen matches{:ok, screen, _diagnostics}.{:error, :no_such_screen}is unchanged, and so is every other function in the module. - Breaking:
Riddler.Screens.validate_screen/3and/4answer{:error, [%Riddler.Finding{code: "response.undecidable"}]}where they answered:okfor a screen carrying a condition the root could not decide; the finding names the node innode_keyand"condition"infield. A button declaringvalidatesasfalseis unaffected and still answers:okwithout running a check. Carry in the root everycontextandresponseskey the document's conditions read, giving a key the visitor has not answered yet its blank value rather than leaving it out, or change the condition to one that decides against a root without it. - A question that asks for the
patternformat and declares apatternthat format cannot compile is now a finding against the document,document.invalid_patternfromRiddler.Screens.Document.validate/1, raised before a visitor arrives. Response validation no longer reports it: the defect is in the document, and nothing a visitor could type would satisfy such a pattern. This is breaking for a host that matched the oldresponse.formatfinding with the fieldpatternon submission for such a question - readdocument.invalid_patternfrom document validation instead, and correct the expression in that question. Apatternon a question that asks for another format, or for none, is unchanged: it is a field nothing consults, and it carries no finding at either layer whatever it says. A question naming thepatternformat and declaring no pattern at all is unchanged too and still answersresponse.formatwith the fieldpattern, under new wording that names the missing pattern rather than calling it unusable. - The document schema is emitted as
schemas/screen-document.schema.json; point a consumer that reads the schema by its old path at the new one. - The
generated_byheadermix riddler.corpuswrites into each emitted case file names the source file and no version, so an emitted corpus is byte-identical across releases; re-emit once to pick up the new header, and point anything that parsed a version out of that string at the request that carried the emit instead. Riddler.Screens.Document.validate/1reports the envelope and boolean shapes the screen document record states, each only where the document carries the field:document.invalid_schema_versionfor aschema_versionother than 1,document.invalid_idfor anidthat is not a string,document.invalid_titlefor a screentitlethat is not a string,document.invalid_requiredfor a question'srequiredthat is not a boolean, anddocument.invalid_validatesanddocument.invalid_stylefor a button'svalidatesthat is not a boolean andstylethat is not a string. A document that carried one of these off-shape validated clean before and now carries a finding; correct the field in the document, or omit it, since an absent field is unchanged and still raises nothing.
Removed
- Breaking:
Riddler.Screens.validate_responses/3and/4are gone; callRiddler.Screens.validate_screen/3or/4with the same root you resolved the screen with, moving the responses map you used to pass into that root under"responses".
Fixed
- A variable used only in the condition of an
unlessis no longer reported as missing, in either render mode, which is what anifcondition already did. Riddler.Template.compile/1andRiddler.Screens.Document.validate/1answer findings rather than raising for a template the parser refuses without saying where, such as{% render %}or{% assign e %}; the finding carries thetemplate.parse_errorcode, no position, and a message that names no place.Riddler.Screens.Document.validate/1tells an author that a node or screen key is not a string instead of telling them there is no key: a key of the wrong form keepsdocument.invalid_keyand now carries a message naming the key that was written, distinct from the message for a key that is absent. A host matching on the message rather than on the code sees the new wording.- A finding's
node_keyis always a string ornil, asRiddler.Finding's typespec has always said. A node whose key was not a string used to put that key on every other finding about the node; those findings now carrynil, the same as a node that declares no key at all, and the key is named in the message. A host indexing findings bynode_keyno longer has to expect a value it cannot look a node up by. - A template that prints the characters of a
{% liquid %}opener from a string literal compiles and renders them, instead of being refused as though it held the tag.
[0.1.0] 2026-09-14
The first release. Riddler is a dynamic content runtime: a host authors content as JSON documents - screens now; emails, images and feature flags forthcoming - and Riddler resolves each against a visitor's context, while the host renders, sends or serves what comes back. A document is admitted and validated on its own, resolved against a host's context and a visitor's responses into the nodes that visitor is shown, its templates compiled and rendered against the subset, and the responses it collects validated against the screen they were shown. The conformance corpus is authored here and emitted into riddler_spec so a second implementation runs the same cases.
Added
Riddler.Template.compile/1accepts a template only when every tag and filter in it is inside the template subset, reporting oneRiddler.Findingper refused construct rather than the first.Riddler.Template.render/3renders a compiled template as text in lenient or strict mode, returning the paths that were missing in lenient and an error carrying them in strict.- A screen document is admitted from decoded JSON and validated on its own, with every reason it is refused reported at once: unknown node types, duplicate or misshapen keys, missing fields, heading levels out of range, conditions that do not parse, templates outside the subset, malformed writes, unknown formats, and variants that are empty or bury a default.
- A visitor's responses are validated against the screen they were shown:
required, theemail,phone,pattern,integerandnumberformats, andminandmaxon the numeric ones, with a question a condition hid unable to fail and a button declaringvalidatesfalse able to submit without any check at all. A question may now carrypattern,minandmaxbeside itsformat. - A screen document resolves against a host's context and a visitor's responses into the nodes that visitor is shown, with hidden nodes absent, every container collapsed to its winner, every template rendered, and what could not be decided reported rather than refused.
mix riddler.corpusemits the conformance corpus and the JSON schemas into a riddler_spec checkout, byte-stable and with agenerated_byheader naming the version and the source file, refusing to emit a corpus this implementation does not satisfy;--checkreports drift instead of writing.- A document's envelope carries
kind, the content kind it belongs to. It is an optional string and it defaults toscreens, so a document that names none is a screen document; the decided kind is carried through to the resolved document, and a kind this package has no runtime for is adocument.unknown_kindfinding naming the value.
Changed
- The screens kind is named after the kind rather than after the nodes inside
a screen:
Riddler.Elementsand everything under it is nowRiddler.Screens, and the corpus capabilitieselements.admit,elements.resolveandelements.validate_responsesare nowscreens.admit,screens.resolveandscreens.validate_responses, emitted fromcorpus/screens/. NoRiddler.Elementsname and noelements.*capability survives this release.templates.renderis unchanged.