[failproofai] feat: unknown flag error with closest-match suggestion + v0.0.1-beta.2#16
Conversation
…0.0.1-beta.2 Unknown flags no longer silently fall through to dashboard launch. The CLI now prints the unrecognized flag and suggests the closest known flag via Levenshtein distance, then exits with code 1. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Free Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe pull request adds CLI validation to detect unknown flags in the command-line interface and suggests the closest matching known flag using Levenshtein distance. Additionally, the package version is incremented from 0.0.1-beta.1 to 0.0.1-beta.2. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Poem
Note 🎁 Summarized by CodeRabbit FreeYour organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://app.coderabbit.ai/login. Comment |
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Summary
--verison) no longer silently fall through to dashboard launch — the CLI now prints the unrecognized flag and suggests the closest known flag via Levenshtein distance, then exits with code 10.0.1-beta.1→0.0.1-beta.2inpackage.jsonTest plan
failproofai --verison→Unknown flag: --verison/Did you mean: --version?, exits 1failproofai --foo→ suggests closest known flag, exits 1failproofai --version→ still prints version, exits 0failproofai --install-policies→ still works normallyfailproofai(no args) → still launches dashboard🤖 Generated with Claude Code
Summary by CodeRabbit
New Features
Chores