René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Discussion on check-consistency","articleBody":"### Description\n\nHi,\r\nI've doubt on how `check-consistency` flag works.\r\n\n\n### Steps to reproduce\n\n1. have a project managed with poetry, with a pyproject.toml like the following\r\n```\r\n[tool.poetry]\r\n    name = \"cool_proj\"\r\n    version = \"2.5.7\"    \u003c\u003c\u003c\u003c this is mandatory for poetry to make the package\r\n...\r\n[tool.commitizen]\r\n    name = \"cz_conventional_commits\"\r\n    version = \"2.5.2\"   \u003c\u003c\u003c\u003c this is mandatory for commitizen\r\n    version_files = [\r\n        \"cool_proj/__init__.py:__version__\",\r\n        \"pyproject.toml:version\"\r\n    ]\r\n```\r\nand `__init__.py` contains\r\n```\r\n__version__ = \"2.5.2\"\r\n```\r\n2. run `poetry run cz bump --check-consistency`\r\n\n\n### Current behavior\n\nthe command works, it prints on stdout\r\n```\r\nBump version: 2.5.2 -\u003e 2.5.3        \u003c\u003c\u003c it takes the value from commitizen's toml section\r\ntag to create: 2.5.3\r\n```\r\n\n\n### Desired behavior\n\nthe expected could be a warning about version not consistent, because at least content of  `__init__.py`  differ from the expected (the one into commitizen's toml section).\r\n\r\nlooking at implementation, also the regex usage has major drawback in this kind of setup, because the regex surely find commitizen's \"version\" attribute, but it can miss the poetry's one, creating package with wrong number (it's taken from poetry section). \n\n### Screenshots\n\n_No response_\n\n### Environment\n\n- commitizen 2.34.0 \r\n- python 3.9.13\r\n- windows 11","author":{"url":"https://github.com/gpongelli","@type":"Person","name":"gpongelli"},"datePublished":"2022-09-23T13:05:17.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":7},"url":"https://github.com/595/commitizen/issues/595"}