fix: use TOML literal multiline strings to avoid parser errors (\0 / unterminated strings) #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Open

giabaotran-2001 wants to merge 1 commit into harish-garg:main from giabaotran-2001:fix/escape-null-byte-in-edge-cases

giabaotran-2001 commented Oct 10, 2025

Fix TOML parse errors caused by escape sequences and unterminated multi-line strings in prompt files by switching from interpreted triple-quoted strings to TOML literal multiline strings.


          Fix error parsing

1ef35e2

OthnielDona commented Oct 17, 2025

Hi! Very useful extension by the bye.

Please apply fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet