Repository navigation
feat(cli)!: render native parse diagnostics - #8
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Parse failures expose argparse or Click messages with an
[interfacy]prefix. Give both backends concise errors, spelling suggestions, and help for the command that failed.diagnostic_layout, independently of help layoutstransform_diagnosticandrender_diagnosticinvoke()silent and expose failure details throughUsageError.diagnosticBreaking Changes
Interfacy.run(), theinterfacycommand, andArgumentParseruse Interfacy messages instead of backend error strings and the[interfacy]prefix. Consumers matching the old text need updated expectations, including forstr(UsageError)Verification
just coverageverifies unknown-command suggestions on both backendscoverage run -m pytest, diagnostic hints identify the simulated script astoolpytestverifies the same hints on Python 3.10, 3.14, 3.15private-inputfrom the error for--unknown=private-input