Skip to content

Readable bugs for Tester: screenshots in issue descriptions print as image files, not raw data - #1701

Draft
Matt Kleinsmith (MattKleinsmith) wants to merge 2 commits into
mainfrom
mattk/issue-images-as-files
Draft

Matt Kleinsmith (MattKleinsmith) wants to merge 2 commits into
mainfrom
mattk/issue-images-as-files

Conversation

@MattKleinsmith

Copy link
Copy Markdown
Contributor

Related to WIZ-12884

Overview of Problem

One base64 screenshot fills Tester's 50 KB shell output cap, hiding every later bug on an issue page.

Overview of Changes

Issue commands save description images as files and print paths; writing paths back re-inlines the images.

Testing

src/domains/publicApi/descriptionImages/descriptionImages.test.ts covers issue get, issue find (one file per distinct image, nothing in base64 left in the output) and the round trip: a description printed by issue get and sent back through issue update reaches the API with the original data URL. It also checks that a missing local image refuses the update and that a team storage path (uploads/...) is left for the platform. Checked the round trip on the real filesystem with a 300 KB WebP.

bun run typecheck
bun run lint
bun run format:check
bun run knip
bun run test

Post-Release Tasks

  • Merge the Version Packages PR so this ships to npm. Tester's ai-task image installs @qawolf/cli@latest when it is built, so Tester gets this from the next ai-task image build after the release.

Checklist

  • Changes follow the code style of this project
  • Self-review completed
  • Tests added/updated (or not applicable)
  • No breaking changes (or described below)

🤖 Generated with Claude Code

Issue descriptions carry screenshots as base64 data URLs. Printed raw,
one screenshot fills an agent's shell output cap and hides the rest of
an issue find page. The CLI now writes each image to a file and prints
its path, and turns local image paths back into data URLs when a
description is written, so a read-then-update keeps every image.

This branch has not been deployed

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

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant