René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[Config loader] check if config key is in package.json before accepting it as a config file","articleBody":"Hello, \r\n\r\nI'm working on a monorepo with backend and frontend and a `.czrc` at the directory's root to enforce commit rules with commitizen.\r\n\r\nAll frontend-related files are in a subdirectory, including the `package.json` file at different filesystem levels.\r\n\r\n**My issue**: In a subdirectory with a package.json between `pwd` and git repository root, `commitizen` seems to acknowledge this file as a configuration file despite the lack of `config.commitizen` key.\r\n\r\n**Fix proposal**: There seems to be a mechanism to check the package.json has a commitizen configuration, but it is commented: https://github.com/commitizen/cz-cli/blob/2e57fd02a5fd2b2dcf89d3235a6956edaeaf672c/src/configLoader/loader.js#L30-L36\r\n\r\nI tried to uncomment it in a local version of commitizen, and it works as expected. \r\nWould it be possible to uncomment it or does it have unwanted side effects?\r\n\r\n","author":{"url":"https://github.com/simrobin","@type":"Person","name":"simrobin"},"datePublished":"2023-06-12T10:04:18.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/975/cz-cli/issues/975"}