Skip to content

Missing nonbinary file contents are silently emitted as an empty complete file #122

Description

@adamtheturtle

Problem

A file object with no contents and no binary:true flag becomes contents:"" without an error. The caller cannot distinguish a genuinely empty source file from an upstream schema omission.

Evidence

assemblePadCodeFiles uses contents ?? "" and only adds an error when rawContents is present and non-null.

Acceptance criteria

  • Mark missing contents on nonbinary files as a schema error/incomplete payload.

Discovered during a systematic audit of CoderPadMCP against its tool schemas and the current CoderPad API contracts.

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions