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

Use stdout when requested to print the configuration #6447

Merged
merged 2 commits into from
Jul 7, 2018
Merged

Use stdout when requested to print the configuration #6447

merged 2 commits into from
Jul 7, 2018

Conversation

mjesun
Copy link
Contributor

@mjesun mjesun commented Jun 12, 2018

When explicitly asking for the config (using --showConfig) we shouldn't honor --useStderr, because in that case, you expect the main output to be your configuration. And, --useStderr was introduced to avoid corrupting JSON coming out as a response; and there is no need for that when requesting the config, because the config is JSON.

@codecov-io
Copy link

codecov-io commented Jun 12, 2018

Codecov Report

Merging #6447 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #6447   +/-   ##
=======================================
  Coverage   63.48%   63.48%           
=======================================
  Files         227      227           
  Lines        8697     8697           
  Branches        4        4           
=======================================
  Hits         5521     5521           
  Misses       3175     3175           
  Partials        1        1

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 47d4370...f4847da. Read the comment docs.

cpojer
cpojer previously requested changes Jun 12, 2018
Copy link
Member

@cpojer cpojer left a comment

Choose a reason for hiding this comment

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

--debug and --showConfig together would now print the same thing twice, to a different pipe.

@mjesun mjesun dismissed cpojer’s stale review June 14, 2018 23:41

Requesting review again

@SimenB
Copy link
Member

SimenB commented Jun 16, 2018

changelog? 🙂

@mjesun
Copy link
Contributor Author

mjesun commented Jun 16, 2018

@SimenB Done! ☺️

@thymikee
Copy link
Collaborator

thymikee commented Jul 7, 2018

ping @cpojer

@cpojer cpojer merged commit 7a0b1d7 into jestjs:master Jul 7, 2018
@mjesun mjesun deleted the use-stdout-for-config branch July 7, 2018 20:57
calebeby pushed a commit to Pigmice2733/scouting-frontend that referenced this pull request Jul 11, 2018
This Pull Request updates dependency [jest](https://github.com/facebook/jest) from `v23.3.0` to `v23.4.0`



<details>
<summary>Release Notes</summary>

### [`v23.4.0`](https://github.com/facebook/jest/blob/master/CHANGELOG.md#&#8203;2340)
[Compare Source](jestjs/jest@v23.3.0...v23.4.0)
##### Features

- `[jest-haste-map]` Add `computeDependencies` flag to avoid opening files if not needed ([#&#8203;6667](`jestjs/jest#6667))
- `[jest-runtime]` Support `require.resolve.paths` ([#&#8203;6471](`jestjs/jest#6471))
- `[jest-runtime]` Support `paths` option for `require.resolve` ([#&#8203;6471](`jestjs/jest#6471))
##### Fixes

- `[jest-runner]` Force parallel runs for watch mode, to avoid TTY freeze ([#&#8203;6647](`jestjs/jest#6647))
- `[jest-cli]` properly reprint resolver errors in watch mode ([#&#8203;6407](`jestjs/jest#6407))
- `[jest-cli]` Write configuration to stdout when the option was explicitly passed to Jest ([#&#8203;6447](`jestjs/jest#6447))
- `[jest-cli]` Fix regression on non-matching suites ([6657](`jestjs/jest#6657))
- `[jest-runtime]` Roll back `micromatch` version to prevent regression when matching files ([#&#8203;6661](`jestjs/jest#6661))

---

</details>




---

This PR has been generated by [Renovate Bot](https://renovatebot.com).
@github-actions
Copy link

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 12, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants