Skip to content
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

[skip ci] - Moving do expression to stage 1 #6943

Merged
merged 6 commits into from
Dec 2, 2017
Merged

[skip ci] - Moving do expression to stage 1 #6943

merged 6 commits into from
Dec 2, 2017

Conversation

rajasekarm
Copy link
Member

@rajasekarm rajasekarm commented Dec 1, 2017

Q                       A
Fixed Issues?
Patch: Bug Fix?
Major: Breaking Change?
Minor: New Feature?
Tests Added + Pass?
Documentation PR
Any Dependency Changes?
License MIT

Based on the spec, we have to move do expression to stage 1 https://github.com/tc39/proposals#stage-1

Copy link
Member

@xtuc xtuc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's still used here https://github.com/rajzshkr/babel/blob/3d7703bf91824481a2296c4b1e2af6f8957ff96c/packages/babel-preset-stage-0/src/index.js#L3

And you need to move this in the stage-1 preset.

Btw the tests didn't catch that.

@babel-bot
Copy link
Collaborator

babel-bot commented Dec 2, 2017

Build successful! You can test your changes in the REPL here: https://babeljs.io/repl/build/6069/

@rajasekarm
Copy link
Member Author

Btw the tests didn't catch that.

I didnt see any test cases to catch this

@hzoo hzoo merged commit c41eb0d into babel:master Dec 2, 2017
@hzoo hzoo added the PR: Spec Compliance 👓 A type of pull request used for our changelog categories label Dec 2, 2017
@rajasekarm rajasekarm deleted the moving-do-stage1 branch December 2, 2017 15:58
@xtuc
Copy link
Member

xtuc commented Dec 3, 2017

Btw the tests didn't catch that.

Sorry I wasn't clear, I meant by this that there's no tests on our presets. Testing the transformations would be too difficult to maintain I think but we can at least test that they are correct Babel plugins.
What do you think?

@lock lock bot added the outdated A closed issue/PR that is archived due to age. Recommended to make a new issue label Oct 5, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Oct 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
outdated A closed issue/PR that is archived due to age. Recommended to make a new issue PR: Spec Compliance 👓 A type of pull request used for our changelog categories
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants