Skip to content

Conversation

@Mohammed-Saajid
Copy link

Fixed #1156

@svlandeg svlandeg self-assigned this Nov 17, 2025
@svlandeg svlandeg added the bug Something isn't working label Nov 17, 2025
@svlandeg svlandeg changed the title Argument(metavar="MY_ARG") has different meaning for the arguments panel compared to the usage text or the non-rich help output #1156 Fix display of metavar argument in Rich formatted help output Nov 17, 2025
@svlandeg svlandeg changed the title Fix display of metavar argument in Rich formatted help output 🐛 Fix display of metavar argument in Rich formatted help output Nov 17, 2025
Copy link
Member

@svlandeg svlandeg left a comment

Choose a reason for hiding this comment

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

Hi @Mohammed-Saajid, thanks for the PR! Can you clarify if any parts of this have been vibe-coded, and if so, which parts?

@Mohammed-Saajid
Copy link
Author

Hi @svlandeg, The Core fix of the bug was manually done. But, tests was generated using AI. Even though I have checked the test file, I'll implement any further changes upon request. Kindly let me know. Thank you and Sorry for inconvenience if any.

@Mohammed-Saajid
Copy link
Author

Betrayal @svlandeg 😔

Copy link
Member

@svlandeg svlandeg left a comment

Choose a reason for hiding this comment

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

The underlying issue here in the code base is pretty complex. For a PR to fix it, ideally you should write the (breaking) unit tests first, commit them, and only then implement and commit the fix. Writing the tests afterwards, especially by vibe coding them, is a kind of self-fulfilling prophecy and gives a false sense of security. Additionally, no explanation was given in the PR body for the fix or the tests, which doesn't help maintainers who need to review this.

I suggest to close this one in favour of #1410, which is more extensive and has more detailed tests taken from user discussions around this topic. Though the general direction of the fix in this PR is correct, some of the tests in #1410 will still fail on this PR.

@svlandeg svlandeg removed their assignment Nov 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Argument(metavar="MY_ARG") has different meaning for the arguments panel compared to the usage text or the non-rich help output

2 participants