Repository navigation
Conversation
* Assert exact output when unwrapped values resemble enclosed syntax. * Cover removal metadata and no-enclosing behavior across the full matrix.
|
Hi @claell — same note across all of your July 16 issues and PRs (#567–#597), apologies for the repetition. Closing this. Passing CI isn't evidence the underlying claim is real — it just means generated tests match generated code. The batch's timing, structure, and forward-referenced numbers point to this being AI-generated rather than manually found and checked, and reviewing it properly would take more effort than a targeted pass over the parser myself. If this fixes something you actually hit: open a small, human-verified PR against a reopened issue with a real repro, and I'll review it in good faith. Any nontrivial design or API choice needs to be discussed and agreed first, not decided inside a PR. Please disclose and verify AI-assisted work before submitting going forward. |
Summary
removed_enclosingmetadata across the full matrix.no-enclosing.Closes #579.
Validation
pytest -p no:cacheprovider -W error tests/middleware_tests/test_enclosing.py: 926 passed, with no skips.tests/test_entrypoint.py.Review note
This is a test-only change. The key judgment is that values beginning and ending with enclosure characters remain valid cases to test: removal interprets those boundary characters as enclosure, while addition configured with
no-enclosingadds nothing and should be checked by exact equality.AI assistance
This pull request was prepared with ChatGPT Codex using GPT-5.6 Sol with high reasoning effort. Codex assisted with test-matrix analysis, branch isolation, and validation. Automated validation is not a substitute for maintainer review.