Hi, I'm the maintainer of jsonrepair-rs. I read your tool-call JSON repair README and saw that your local fork of 0.2.1 keeps #, //, and /* ... */ as content when a model omits an opening quote. That is a useful, concrete gap in the upstream default policy.
I'm looking for real requirements before designing an upstream option. Could you share a synthetic minimal input and expected output for that case, plus any other malformed streamed tool arguments your fork handles differently? I would also appreciate knowing whether an explicit option that preserves comment markers in tool-call arguments would let you use upstream, or whether other behavior or performance constraints require the fork.
Please avoid posting real user/tool payloads or credentials. A small fabricated reproducer is enough. Thanks for documenting the fork so clearly.
Hi, I'm the maintainer of
jsonrepair-rs. I read your tool-call JSON repair README and saw that your local fork of 0.2.1 keeps#,//, and/* ... */as content when a model omits an opening quote. That is a useful, concrete gap in the upstream default policy.I'm looking for real requirements before designing an upstream option. Could you share a synthetic minimal input and expected output for that case, plus any other malformed streamed tool arguments your fork handles differently? I would also appreciate knowing whether an explicit option that preserves comment markers in tool-call arguments would let you use upstream, or whether other behavior or performance constraints require the fork.
Please avoid posting real user/tool payloads or credentials. A small fabricated reproducer is enough. Thanks for documenting the fork so clearly.