-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
program.emit
behavior seems to be broken in 2.11.0
#659
Comments
Could you give me sample code that does not work as expected so that there is no discrepancy in recognition? |
I'll try to make a PR addressing this issue today. |
Discussed issue was introduced in https://github.com/tj/commander.js/pull/494/files In user code @abetomo, what do you think? |
Yep, @Flackus you are right, we should merge it in major release, but instead break compatibility in minor release. As things already done, we cannot rollback updates, but instead we can add notice to README.md about the breakage between 2.10 and 2.11 versions. |
@vanesyan yeah, you're right, no reason to break things twice. |
commander@2.11.0 is a broken change release see tj/commander.js#659 closes #210
commander@2.11.0 is a broken change release see tj/commander.js#659 closes #210 pick from #211
commander@2.11.0 is a broken change release see tj/commander.js#659 closes #210
commander@2.11.0 is a broken change release see tj/commander.js#659 closes #210 pick from #211
This issue has not had any activity in over six months. It isn't likely to get acted on due to this report. Feel free to open a new issue if it comes up again, with new information and renewed interest. Thank you for your contributions. |
Somewhere between those two versions the following case was broken. We have two subcommands, let's name them
start
anddownload
. Inside the code for thestart
command we doprogram.emit('download');
.It works for
2.10.0
, but in2.11.0
download
subcommand will not be triggered.The text was updated successfully, but these errors were encountered: