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

fix context for beforeEach and afterEach hooks in Flow type definition file #1344

Merged
merged 6 commits into from
Apr 10, 2017

Conversation

zs-zs
Copy link
Contributor

@zs-zs zs-zs commented Apr 6, 2017

Fixes #1340

@novemberborn
Copy link
Member

@gajus does this work for you?

@gajus
Copy link

gajus commented Apr 6, 2017

This works. 👍

@zs-zs
Copy link
Contributor Author

zs-zs commented Apr 6, 2017

I have no idea why it failed for node 4...

Copy link
Member

@novemberborn novemberborn left a comment

Choose a reason for hiding this comment

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

I have no idea why it failed for node 4...

Looks like a fluke. I just kicked off a rebuild.

@@ -25,11 +25,6 @@ test.cb(t => {
t.end();
});

test.beforeEach(t => {
// $ExpectError: Unknown property "context"
Copy link
Member

Choose a reason for hiding this comment

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

Perhaps keep the beforeEach, but remove this $ExpectedError line.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I thought about keeping the beforeEach, but then I thought it has nothing to with the issue #1114. But maybe it has, I didn't dig deeper.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

BTW, how to trigger a rebuild? I didn't find that, never used Appveyor before.

Copy link
Member

Choose a reason for hiding this comment

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

It's used elsewhere in this file, so might be best to keep it.

I think you have to be in the AppVeyor team to do that.

Copy link
Member

@sindresorhus sindresorhus Apr 6, 2017

Choose a reason for hiding this comment

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

You can also push an empty commit or force push, to trigger a rebuild.

@novemberborn
Copy link
Member

I think this is good now. I suppose the changes may break something because some types have been removed? But even if so it seems like a good bugfix that we should just ship in a 0.19.1 release.

@zs-zs
Copy link
Contributor Author

zs-zs commented Apr 6, 2017

Hm I don't know. I only removed "dead" types, so I hope it won't break anything.

@gajus
Copy link

gajus commented Apr 8, 2017

Whats the shipping plan?

This reverts commit a1a8195.
@novemberborn novemberborn merged commit d169f0e into avajs:master Apr 10, 2017
@novemberborn
Copy link
Member

Thanks @zs-zs! I took out the dead type removal, we'll land that later: #1352

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.

4 participants