René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Use named capture group in bump_pattern to enable stricter check","articleBody":"**Goal**\r\nmake regular expression pattern stricter so that we won't accidentally match things we don't need\r\n\r\n**Description**\r\nIn [commitizen/cz/conventional_commits/conventional_commits.py#L33](https://github.com/Woile/commitizen/blob/command-changelog/commitizen/cz/conventional_commits/conventional_commits.py#L33) on `command-changelog` branch, I use named capture group so that we could use a stricter regular expression like `.*\\n\\nBREAKING CHANGE`. The benefit of it is that we don't have to break the whole commit message into lines like [commitizem/bump.py#L31](https://github.com/Woile/commitizen/blob/v1.16.0/commitizen/bump.py#L31). It can also avoid bump or generate changelog based on commit message like `fix ---  it does not follow the rule but still match the pattern`.\r\nAnother thought on this topic is that we probably merge the `bump_map` and `bump_pattern` into one some data class to store `name`(e.g., `break`), `pattern`(e.g., `.*\\n\\nBREAKING CHANGE`), `behavior`(e.g., `PATCH`).","author":{"url":"https://github.com/Lee-W","@type":"Person","name":"Lee-W"},"datePublished":"2020-01-29T04:28:27.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":11},"url":"https://github.com/129/commitizen/issues/129"}