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

Silent mode #60

Closed
elicwhite opened this issue Oct 21, 2015 · 4 comments
Closed

Silent mode #60

elicwhite opened this issue Oct 21, 2015 · 4 comments
Labels
improvement

Comments

@elicwhite
Copy link
Member

I'm writing tests for my codemods and thus running jscodeshift repeatedly in my tests. There is a lot of information printed for every run:

Processing 1 files...
Spawning 1 workers with 1 files each...
Running in dry mode, no files will be written!
All workers done.
Results: 0 errors 0 unmodifed 0 skipped 1 ok
Time elapsed: 0.902 seconds

It would be nice if there was a silent mode. The information printed could be provided as a data object at the end as per #59
@fkling
Copy link
Contributor

fkling commented Oct 21, 2015

These are all good ideas :) 👍

@cpojer
Copy link
Contributor

cpojer commented Oct 21, 2015

@TheSavior would you mind sending a Pull Request for this? :)

@elicwhite
Copy link
Member Author

I can't prioritize working on that currently. @cpojer helped me in my other ticket by showing me the trick to run the transform directly instead of using the runner which got me around this problem for now.

@Sinewyk Sinewyk mentioned this issue Dec 17, 2015
Merged
@fkling
Copy link
Contributor

fkling commented Dec 19, 2015

Closed with d3bba64.

@fkling fkling closed this as completed Jan 7, 2016
euphocat pushed a commit to euphocat/jscodeshift that referenced this issue Oct 22, 2017
@alangpierce @cpojer
Document bug in create-element-to-jsx, add Contributing section (face…
6c4a2b3 
…book#60)

As mentioned in reactjs/react-codemod#59 , the
`create-element-to-jsx` codemod can destroy comments, so leave a warning in the
docs so people know to be careful.

Also add a "Support and Contributing" section at the bottom of the README that
briefly describes the state and purpose of the repo and how contributions are
handled.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
improvement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@cpojer @fkling @elicwhite