Skip to content

fix: support object values in coerce handlers - #547

Open
amtbsl wants to merge 2 commits into
yargs:mainfrom
amtbsl:fix/coerce-object-values-352
Open

fix: support object values in coerce handlers#547
amtbsl wants to merge 2 commits into
yargs:mainfrom
amtbsl:fix/coerce-object-values-352

Conversation

@amtbsl

@amtbsl amtbsl commented Aug 29, 2026

Copy link
Copy Markdown

Fixes #352.

Avoid treating object-valued options as arrays during coercion. Coerce handlers now receive object values directly, with targeted regression coverage.

Validation: TypeScript compile and targeted object-coercion regression test.

@shadowspawn

Copy link
Copy Markdown
Member

To be clear: is this Pull Request entirely AI/LLM generated?

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.

maybeCoerceNumber bombs if coerce produced an object without toString

2 participants