Skip to content

fix: handle digits and multiple segments in option camelcasing - #181

Open
feritcemkahraman wants to merge 1 commit into
cacjs:mainfrom
feritcemkahraman:fix/camelcase-numbers
Open

feritcemkahraman wants to merge 1 commit into
cacjs:mainfrom
feritcemkahraman:fix/camelcase-numbers

Conversation

@feritcemkahraman

Copy link
Copy Markdown

Summary

Option names containing digits (e.g. --step-1-name, --utf-8-mode, --web-v2-api, --api-v1-key) failed to camelcase properly on parsed options.

The previous regex ([a-z])-([a-z])\ strictly expected lowercase ASCII characters before and after the hyphen and consumed matching characters, which left consecutive single-character segments (such as -1-\ or -v2-) uncamelcased or partially matched with trailing hyphens (\step-1-name\ remained \step-1-name, \web-v2-api\ became \webV2-api).

Updating the replacement regex to /-+([a-z\d])/gi\ ensures hyphens followed by letters or digits are consistently converted to camelCase.

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.

1 participant