Skip to content

fix: s-string escaping#5497

Merged
max-sixty merged 2 commits intoPRQL:mainfrom
gosupersimple:fix-5496-s-string-escape
Oct 15, 2025
Merged

fix: s-string escaping#5497
max-sixty merged 2 commits intoPRQL:mainfrom
gosupersimple:fix-5496-s-string-escape

Conversation

@priithaamer
Copy link
Copy Markdown
Contributor

Attempting to fix regression #5496 that was working in 0.13.4

Fixes s-strings terminating when they contain double quote.
@max-sixty
Copy link
Copy Markdown
Member

thanks @priithaamer !

can we avoid doing a full integration test for each change if possible? hopefully this can just be a small inline insta test (ideally same with #5495)

(also OK if we merge, release, and then I'll ask Claude to make these smaller — wdyt?)

@max-sixty
Copy link
Copy Markdown
Member

I made the changes — it's at max-sixty@7a821b8a

can you enable "Allow edits from maintainers" so I can push to this branch?

…ping

Replace the comprehensive integration test with a focused inline test that
verifies escaped quotes in s-strings round-trip correctly through parse and
format. The lexer already has coverage for tokenization of escaped quotes.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
@priithaamer
Copy link
Copy Markdown
Contributor Author

Hey, thanks for the changes, i merged them myself. Should be less trouble for you.

Totally fine to use the inline tests -- i was a bit unsure about integration tests as well.

This and #5495 are last remaining blockers for us to upgrade from 0.13.4 and close several issues / improvements in our product.

@max-sixty max-sixty merged commit f8593cb into PRQL:main Oct 15, 2025
36 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.

2 participants