Skip to content

[Fix] stringify: use configured delimiter after charsetSentinel#555

Merged
ljharb merged 1 commit into
ljharb:mainfrom
deepview-autofix:deepview/a8b186eabe
Apr 27, 2026
Merged

[Fix] stringify: use configured delimiter after charsetSentinel#555
ljharb merged 1 commit into
ljharb:mainfrom
deepview-autofix:deepview/a8b186eabe

Conversation

@deepview-autofix

Copy link
Copy Markdown
Contributor

The utf8=... charset sentinel was followed by a hardcoded &, ignoring options.delimiter. With any non-& delimiter the output mixed delimiters (e.g. utf8=%E2%9C%93&a=1;b=2), breaking self round-tripping. Emit the configured delimiter instead, and add a regression test.

The `utf8=...` charset sentinel was followed by a hardcoded `&`, ignoring `options.delimiter`.
With any non-`&` delimiter the output mixed delimiters (e.g. `utf8=%E2%9C%93&a=1;b=2`), breaking self round-tripping.
Emit the configured delimiter instead, and add a regression test.

Co-Authored-By: Claude <noreply@anthropic.com>
Co-Authored-By: DeepView Autofix <276251120+deepview-autofix@users.noreply.github.com>
Co-Authored-By: Nikita Skovoroda <chalkerx@gmail.com>
Signed-off-by: Nikita Skovoroda <chalkerx@gmail.com>
@ljharb ljharb force-pushed the deepview/a8b186eabe branch from 283055a to a0a81ea Compare April 27, 2026 17:04
@ljharb ljharb merged commit a0a81ea into ljharb:main Apr 27, 2026
598 of 601 checks passed
@AmedeoPelliccia

Copy link
Copy Markdown

And thnks

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

Labels

None yet

3 participants