-
Notifications
You must be signed in to change notification settings - Fork 202
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: add option usePreparedCommit default false #196
Conversation
8f40917
to
27a5ef5
Compare
ISSUES CLOSED: #173
27a5ef5
to
bd3af82
Compare
ISSUES CLOSED: #173
It's just pending unit test coverage. Also considering making this a breaking change since the default is now "false" for usePreparedCommit. Before it was kind of "true". I am away this week. I'll be able to write the tests mid-next week. |
Sounds good!, thanks man |
…ggest, interrupting the flow With the introduction of http://leoforfree/cz-customizable#122, cz-customizable pre-populates the subject and the body of the commit message with whatever values the _previous_ commit message had. When a commit message is long, this interrupts the developer workflow as a lengthy, non-editable string of text derived from the previous commit takes up all the space for the _current_ commit and confuses Inquirer CLI, which starts to render the cursor in an invalid location Related tickets: re leoforfree/cz-customizable#196, re leoforfree/cz-customizable#196
…ggest, interrupting the flow With the introduction of leoforfree/cz-customizable#122, cz-customizable pre-populates the subject and the body of the commit message with whatever values the _previous_ commit message had. When a commit message is long, this interrupts the developer workflow as a lengthy, non-editable string of text derived from the previous commit takes up all the space for the _current_ commit and confuses Inquirer CLI, which starts to render the cursor in an invalid location Related tickets: re leoforfree/cz-customizable#173, re leoforfree/cz-customizable#196
…ggest, interrupting the flow With the introduction of leoforfree/cz-customizable#122, cz-customizable pre-populates the subject and the body of the commit message with whatever values the _previous_ commit message had. When a commit message is long, this interrupts the developer workflow as a lengthy, non-editable string of text derived from the previous commit takes up all the space for the _current_ commit and confuses Inquirer CLI, which starts to render the cursor in an invalid location Related tickets: re leoforfree/cz-customizable#173, re leoforfree/cz-customizable#196
This issue has been bothering me, I hope this PR can be merged in time. |
@docker-soga I'll try to address the code coverage today so we can merge it. I think this is a breaking change as it changes the default option. |
…z-customizable into fix-usePreparedCommit
I am not sure if people use this option but it is likely to be deprecated. BREAKING CHANGE: now usePreparedCommit is false. Please update your .cz-config with usePreparedCommit: true if you like to continue using.
I am really thinking if we need this option |
89e227e
to
bfe9214
Compare
fix: add option usePreparedCommit default false
TODO: it needs unit tests for coverage
ISSUES CLOSED: #173