-
Notifications
You must be signed in to change notification settings - Fork 36
Feature request: Support additional prompts defined by commitizen adapters #5
Comments
Nice idea |
Downside would be that a commitizen adaptor might try to read from stdin directly, which we couldn't intercept. |
Overwriting |
I'm using |
@yetithefoot I don't think that its a good idea to rely on a format which is inquirer dependent. That ties this format into this dependency. But you are right with the idea that the workflow in this extension should be configurable or extensible. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Some custom commitizen configs define additional prompts (eg. https://github.com/atlassian/cz-lerna-changelog needs to know which packages in a monorepo to count a change as affecting).
Would be nice if vscode-commitizen could support these too. Maybe instead of hardcoding the series prompts, it could defer to the installed commitizen adaptor (perhaps by passing in a custom io interface in place of commitizen's inquirer.js instance?).
The text was updated successfully, but these errors were encountered: