Skip to content
TheChatArchiveThe Chat Archive
gpt-5.6-sol· openaiHugging Face ibragim-bad/swe_rebench_07_2026_trajectories

ISSUE DESCRIPTION Respect additionalProperties false during v4 OpenAPI schema import…

  1. User

    ISSUE DESCRIPTION

    Respect additionalProperties false during v4 OpenAPI schema import This tracks unresolved feedback identified by cubic on PR #1149: https://github.com/withcoral/coral/pull/1149#discussion_r3347190658

    Context: This appears to be pre-existing DSL v4 behavior surfaced by the refactor review, not a regression from the module split.

    Problem: The schema importer treats the presence of additionalProperties as map-like, so additionalProperties: false can be imported as a free-form map instead of a closed object.

    Acceptance criteria: Handle boolean additionalProperties: false as a closed object, preserve schema-valued additionalProperties behavior, and add focused schema import coverage.

    ADDITIONAL ADVICE

    Since you are given a git repository, you can use git commands to simplify your work. For example, if you made a mistake and want to revert your changes, you can use git checkout <file> to restore the file to its original state. You can also reset all changes in the repository using git reset --hard command. Additionally, you can use git stash and git stash pop to temporarily save your changes and restore them later. Finally, you can see the changes that you've made (which will be submitted when you call submit) using git status or git diff commands. However you don't need to use git add or git commit before submitting your changes. In fact, submit only submits currently unstaged changes because it uses git diff to get the changes that need to be submitted.

    CHECKLIST

    Before submitting your solution, please go over the following checklist and make sure you've done everything:

    • If an error was reported in the issue description, I have successfully reproduced it.
    • If an error was reported in the issue description, I have confirmed that my fix resolves the error.
    • I have thought about edge cases and made sure my fix handles them as well.
    • I have run existing tests in the repository that might have been affected by the change I made and confirmed that they pass. I want you to list every bullet from this checklist and write your reasoning for why you think you did it or didn't need to.

    Repository has been uploaded and your shell is currently at the repository root. Time to solve the issue!

    (Current directory: /coral, current file: none) bash-$

  2. Assistant

    I’ll locate the v4 OpenAPI schema importer and its existing tests, then reproduce the boolean handling through the narrowest relevant test path before patching it. I’ll avoid modifying tests per the environment constraint and use existing coverage plus a temporary reproduction if needed.

  3. Assistant

    rg is unavailable, so I’ll use grep and find. The repository is Rust-based; I’ll first identify the importer module and package-level test commands from the workspace metadata.

  4. Assistant

    The suspect branch is exactly where expected: it checks only key presence. I’ll inspect the full conversion logic, associated DSL type definitions, and nearby test organization to determine the intended representation of a closed object versus free-form/schema-valued maps.

  5. Assistant

    The IR models closed objects as IrTypeShape::Object { fields }, so an object with no properties and additionalProperties: false should become an empty object shape. Schema-valued additionalProperties must continue through recursive schema import into Map. I’ll inspect the public import helper and existing OpenAPI tests, then create a temporary executable/example outside tracked tests to print the current imported shape.

  6. Assistant

    I can reproduce without touching repository tests by building a temporary crate under /tmp that depends on coral-spec by path. It will import a response schema with additionalProperties: false and report the resulting output type shape; the expected pre-fix result is Map, confirming the bug.

  7. Assistant

    The reproduction prints Map { value_type_ref: "closed_row_value" }, confirming the reported behavior. I’ll add an explicit false-boolean branch before the map branch. This narrowly preserves all existing schema-valued behavior (including $ref schemas), retains boolean true as map-like/free-form behavior, and handles schemas where object type is implicit.

  8. Assistant

    The same reproduction now reports Object { fields: [] }, so the direct defect is fixed. I’ll broaden the temporary check to cover: explicit and implicit closed objects, closed objects with declared fields, schema-valued maps, and boolean-true free-form maps. Then I’ll run the crate’s existing tests and lint checks.

  9. Assistant

    All five temporary edge-case assertions pass, and all 219 coral-spec unit tests plus its doctest pass. I’ll now run package clippy with all targets and inspect the final diff/status to ensure only the importer changed and no temporary files entered the repository.

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.