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.

Sign up for GitHub

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

Jump to bottom

Ensure that generator functions always have an identifier - fixes T6733 #3119

Merged
merged 1 commit into from
Dec 2, 2015
Merged

Ensure that generator functions always have an identifier - fixes T6733 #3119

merged 1 commit into from
Dec 2, 2015

Conversation

loganfsmyth
Copy link
Member

@codecov-io
Copy link

Current coverage is 84.59%

Merging #3119 into master will decrease coverage by -0.26% as of a675234

@@            master   #3119   diff @@
======================================
  Files          214     214       
  Stmts        15547   15549     +2
  Branches      3314    3314       
  Methods          0       0       
======================================
- Hit          13193   13154    -39
- Partial        676     715    +39
- Missed        1678    1680     +2

Review entire Coverage Diff as of a675234

Powered by Codecov. Updated on successful CI builds.

@hzoo
Copy link
Member

hzoo commented Dec 1, 2015

Haha I made this change a while ago in #2858 but then reverted since another pr fixed the bug it was for fa78aba 👍

hzoo added a commit that referenced this pull request Dec 2, 2015
@hzoo
Merge pull request #3119 from loganfsmyth/default-export-generator-6733
53877ec 
Ensure that generator functions always have an identifier - fixes T6733
@hzoo hzoo merged commit 53877ec into babel:master Dec 2, 2015
@loganfsmyth loganfsmyth deleted the default-export-generator-6733 branch December 2, 2015 04:19
@loganfsmyth
Copy link
Member Author

Thanks for merging!

@babel-bot babel-bot mentioned this pull request Sep 7, 2016
Closed
@lock lock bot added the outdated A closed issue/PR that is archived due to age. Recommended to make a new issue label Oct 8, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Oct 8, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers
No reviews
Assignees
No one assigned
Labels
outdated A closed issue/PR that is archived due to age. Recommended to make a new issue
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@loganfsmyth @codecov-io @hzoo