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

refactor: use create-jest-runner #37

Merged
merged 5 commits into from
Apr 27, 2018
Merged

refactor: use create-jest-runner #37

merged 5 commits into from
Apr 27, 2018

Conversation

SimenB
Copy link
Member

@SimenB SimenB commented Mar 27, 2018

Closes #32
Closes #36
Fixes #23
Fixes #20

Closes #32
Closes #36
Fixes #23
Fixes #20
@SimenB SimenB requested review from ljharb and rogeliog March 27, 2018 17:06
],
jestTestPath: testPath,
});
const runESLint = ({ testPath, config }) => {
Copy link
Member Author

Choose a reason for hiding this comment

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

@@ -6,7 +6,7 @@ exports[`Works when it has failing tests 1`] = `
4:3 error 'hello' is not defined no-undef
5:3 error 'bye' is not defined no-undef
✖ 2 problems (2 errors, 0 warnings)
ESLint
ESLint
Copy link
Member Author

Choose a reason for hiding this comment

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

not sure about this one... @rogeliog thoughts?

Copy link
Collaborator

Choose a reason for hiding this comment

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

This should definitely be a blocker; the check shouldn’t appear if there are any failures.

Copy link
Member Author

Choose a reason for hiding this comment

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

yup. it was a bug in my port, fixed now 🙂

@@ -6,7 +6,7 @@ exports[`Works when it has failing tests 1`] = `
4:3 error 'hello' is not defined no-undef
5:3 error 'bye' is not defined no-undef
✖ 2 problems (2 errors, 0 warnings)
ESLint
ESLint
Copy link
Collaborator

Choose a reason for hiding this comment

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

This should definitely be a blocker; the check shouldn’t appear if there are any failures.

@@ -16,7 +16,7 @@ mocked-stack-trace 3 | if (a === 2) {
6 | }
7 |
2 errors found.
ESLint
ESLint
Copy link
Collaborator

Choose a reason for hiding this comment

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

Also here

Copy link
Collaborator

@ljharb ljharb left a comment

Choose a reason for hiding this comment

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

Seems good; it’s a major refactor tho so more eyes are probably good.

Copy link
Member

@rogeliog rogeliog left a comment

Choose a reason for hiding this comment

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

This is awesome! Thanks!

@ljharb
Copy link
Collaborator

ljharb commented Mar 29, 2018

This should be a patch, but it’s a risky one, so whoever merges and releases it, please keep an eye out for failed greenkeeper issues popping up.

@SimenB
Copy link
Member Author

SimenB commented Mar 29, 2018

I'd say it's a minor (because of added support for run in band), but I agree it comes with some risk.

I don't use this runner, could someone who do try to run it on their code base as a sanity check?

@ljharb
Copy link
Collaborator

ljharb commented Mar 29, 2018

Ah true, minor is good.

I’m traveling this week but will try it on Airbnb’s codebase on Monday if it’s not merged by then.

@rogeliog rogeliog changed the title refactor: use jest-create-runner refactor: use create-jest-runner Mar 29, 2018
@rogeliog
Copy link
Member

@ljharb awesome, thanks for that! Yes I think we can wait 😄

@SimenB
Copy link
Member Author

SimenB commented Apr 14, 2018

@ljharb did you get a chance to test it out?

@ljharb
Copy link
Collaborator

ljharb commented Apr 14, 2018

aah, sorry, no i didn’t yet. I’ll try to make some time to do it next week or the week after!

@ljharb
Copy link
Collaborator

ljharb commented Apr 22, 2018

My work laptop's died on me, so I'm not sure when I'll be able to test this PR :-/

I don't think that needs to block it, though.

@SimenB
Copy link
Member Author

SimenB commented Apr 23, 2018

I tested it in https://github.com/jest-community/eslint-plugin-jest, and it works fine there.

@rogeliog thoughts on merging and publishing?

@rogeliog rogeliog merged commit e5f89b0 into master Apr 27, 2018
@rogeliog
Copy link
Member

I just published it under 0.5.0

@ljharb ljharb deleted the create-jest-runner branch April 27, 2018 04:27
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.

3 participants