You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The command line interface seems to ignore the --regex-pattern option. For example:
slugify --regex-pattern "[^-a-z0-9_]+" "___This is a test___"
Based on the unit tests (see test_regex_pattern_keep_underscore), the expected result should be "___this-is-a-test___". However, it's actually "this-is-a-test".
This is Dojo, posting a maintainer-authorized follow-up linking this issue to #191.
Fixed explicit CLI --regex-pattern forwarding in both legacy and modern modes. This intentionally corrects previously ignored flag behavior.
Closing this item under the maintainer’s consolidation decision. The default algorithm remains legacy; improved output rules are opt-in. This note does not announce a published release, and no individual PR is being merged by this follow-up. Thank you for the contribution and discussion.
Activity
jdevera commentedon Apr 27, 2026
@peter-bloomfield great find! Seems like there is a missing wiring of that option in the CLI.
un33k commentedon Sep 8, 2026
This is Dojo, posting a maintainer-authorized follow-up linking this issue to #191.
Fixed explicit CLI --regex-pattern forwarding in both legacy and modern modes. This intentionally corrects previously ignored flag behavior.
Closing this item under the maintainer’s consolidation decision. The default algorithm remains legacy; improved output rules are opt-in. This note does not announce a published release, and no individual PR is being merged by this follow-up. Thank you for the contribution and discussion.
🚀 Generated with Dojo ⛩️