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

Flow opaque type 6.x backport #6081

Merged
merged 5 commits into from Aug 15, 2017
Merged

Flow opaque type 6.x backport #6081

merged 5 commits into from Aug 15, 2017

Conversation

jbrown215
Copy link
Contributor

Q A
Patch: Bug Fix? No
Major: Breaking Change? No
Minor: New Feature? Yes
Deprecations? No
Spec Compliancy? Yes
Tests Added/Pass? Yes
Fixed Tickets N/A
License MIT
Doc PR No
Dependency Changes None

Backport of #5990. Depends on babel/babylon#644

I added all the same tests (with some slight changes) to babel-generator, babel-plugin-transform-flow-strip-types, and babel-plugin-transform-flow-comments.

Note: When using the current state of 6.x on both babel and babylon, there were two tests errors:
bin/babel-node v8Flag-dashed-with-param and bin/babel-node v8Flag-underscored-with-param

This diff will also have those errors

@jbrown215 jbrown215 changed the title 6.x Flow opaque type 6.x backport Aug 9, 2017
@xtuc xtuc added 6.x: backport area: flow PR: Spec Compliance 👓 A type of pull request used for our changelog categories labels Aug 11, 2017
@bradennapier
Copy link

Looking forward to this!

@jbrown215 jbrown215 changed the base branch from 6.x to master August 15, 2017 19:50
@jbrown215
Copy link
Contributor Author

@hzoo changed target to master and bumped babylon in babel-core, babel-generator, babel-traverse, and babel-types to 6.18.0

@hzoo hzoo merged commit c28465e into babel:master Aug 15, 2017
@jbrown215
Copy link
Contributor Author

@hzoo: the build is broken for the same reason it was broken in the pr to 7.0. I'm going to backport @existentialism's fix (#6031) and put up another PR to master

@hzoo
Copy link
Member

hzoo commented Aug 15, 2017

cool, thanks. it's fine locally?

@jbrown215
Copy link
Contributor Author

problem repros locally, but with changes from #6031 everything is fine

@lock lock bot added the outdated A closed issue/PR that is archived due to age. Recommended to make a new issue label Oct 6, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Oct 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
6.x: backport area: flow 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.

None yet

4 participants