Skip to content

docs: fix stale signature output in Elixir README examples#6088

Open
prql-bot wants to merge 1 commit into
mainfrom
docs/elixir-readme-signature
Open

docs: fix stale signature output in Elixir README examples#6088
prql-bot wants to merge 1 commit into
mainfrom
docs/elixir-readme-signature

Conversation

@prql-bot

Copy link
Copy Markdown
Collaborator

Nightly survey finding. The Basic Usage examples in the Elixir binding README (also rendered in the book at project/bindings/elixir.md) showed stale output:

  • The signature comment was pinned to -- Generated by PRQL compiler version 0.3.1 (https://prql-lang.org). The version is long out of date (workspace is now 0.13.x), and the format itself changed — the current signature is -- Generated by PRQL compiler version:{version} {target}(https://prql-lang.org) (note the colon and target segment; see prqlc/src/sql/mod.rs).

Rather than re-pin a version that will drift again, this matches the convention the binding's own @doc doctests already use (lib/prql.ex): pass signature_comment: false so the example output is the stable SQL only. The new README output is copied verbatim from those mix test-verified doctests, so it stays correct across version bumps.

No separate regression test: the README prose isn't executed, but the outputs shown are exactly the strings asserted by the existing lib/prql.ex doctests, which CI runs.

The examples pinned `compiler version 0.3.1` and an outdated signature
format. Mirror the binding's own doctests (`signature_comment: false`) so
the shown output is the stable SQL and doesn't drift with each release.
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