Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork9.7k
Revert "bug #21841 [Console] Do not squash input changes made from console.command event (chalasr)"#22027
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Merged
Uh oh!
There was an error while loading.Please reload this page.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters
Member
fabpot commentedMar 22, 2017
Thank you@chalasr. |
fabpot added a commit that referenced this pull requestMar 22, 2017
…ade from console.command event (chalasr)" (chalasr)This PR was merged into the 2.8 branch.Discussion----------Revert "bug#21841 [Console] Do not squash input changes made from console.command event (chalasr)"| Q | A| ------------- | ---| Branch? | 2.8| Bug fix? | no| New feature? | no| BC breaks? | no| Deprecations? | no| Tests pass? | yes| Fixed tickets |#21953,#22050| License | MIT| Doc PR | n/aA bit frustrated to revert this change since the BC break report lacks of information, making us unable to reproduce nor to look at improving the situation.I'm going to re-propose this on master, covering the BC break that is identified, fixed and tested using the changes made in#21953. That will let the choice for the reporter to upgrade using the 1 required LOC.Commits-------5af47c4 Revert "bug#21841 [Console] Do not squash input changes made from console.command event (chalasr)"
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading.Please reload this page.
A bit frustrated to revert this change since the BC break report lacks of information, making us unable to reproduce nor to look at improving the situation.
I'm going to re-propose this on master, covering the BC break that is identified, fixed and tested using the changes made in#21953. That will let the choice for the reporter to upgrade using the 1 required LOC.