Skip to content

version-gate the changes from #3618 and #3632 #3730

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

Closed
wants to merge 1 commit into from
Closed

Conversation

scampi
Copy link
Contributor

@scampi scampi commented Aug 5, 2019

part of #3721

@topecongiro
Copy link
Contributor

I am not sure whether it is a good idea to add a version gate to the features that have been already shipped and released as the default. It would mean that we are introducing yet another breaking change to the default formatting. It's a shame that we broke the stability guarantee, but I don't feel that fixing them afterward does anything good to users.

@scampi
Copy link
Contributor Author

scampi commented Aug 6, 2019

Yeah I think you're right. How do we communicate those formatting changes to solve #3721 ?

BTW I will make a new commit to #3680 for gate-keeping the formatting changes there...

@scampi scampi closed this Aug 6, 2019
@scampi scampi deleted the gate-unicode branch August 6, 2019 07:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants