Thanks to visit codestin.com
Credit goes to github.com

Skip to content

feat: tell the user how to run suggested assertions#64

Merged
PeterKneale merged 2 commits into
mainfrom
suggest-run-hint
Jun 25, 2026
Merged

feat: tell the user how to run suggested assertions#64
PeterKneale merged 2 commits into
mainfrom
suggest-run-hint

Conversation

@PeterKneale

Copy link
Copy Markdown
Owner

What

After bioassert suggest <file> writes the assertions file, it now prints a follow-up hint line showing exactly how to run the result:

Wrote 2 assertions to LICENSE.assertions.txt
Review and tighten them, then run: bioassert run LICENSE.assertions.txt

Previously it only printed the Wrote N assertions to <path> line, leaving the next step implicit. The hint also nudges the author to review and tighten the heuristic suggestions before relying on them, matching the design philosophy that suggestions are guesses from the current file rather than verified expectations.

Changes

  • src/main.rs — add a second println! after the "Wrote" line in run_suggest.
  • specs/suggest.md — document the new hint line in the message-format sections.

Testing

  • cargo build clean.
  • cargo test suggest — all 5 suggest integration tests pass. The success message is not snapshotted, so no snapshots needed updating.
  • Manual run against a real file confirms the new two-line output.

🤖 Generated with Claude Code

After `suggest` writes the assertions file, print a follow-up hint line
showing the exact `bioassert run <path>` command, with a nudge to review
and tighten the heuristic suggestions first.

Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
Copilot AI review requested due to automatic review settings June 25, 2026 07:02

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR improves the UX of bioassert suggest <file> by printing an explicit next-step hint after writing the generated assertions file, and updates the suggest specification to document the new two-line success output.

Changes:

  • Add a follow-up println! in run_suggest that tells users exactly how to run the generated assertions file.
  • Update specs/suggest.md to document the new hint line in the success message format.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File Description
src/main.rs Prints an additional success hint showing the exact bioassert run <path> command after generating assertions.
specs/suggest.md Documents the updated stdout message format to include the new hint line.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread src/main.rs
Comment on lines +125 to +128
println!(
"Review and tighten them, then run: bioassert run {}",
output_path.display()
);
@PeterKneale PeterKneale merged commit 4f1d2a1 into main Jun 25, 2026
3 checks passed
@PeterKneale PeterKneale deleted the suggest-run-hint branch June 25, 2026 07:10
@github-actions github-actions Bot mentioned this pull request Jun 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants