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

Different --silent use case #336

Open
eviefp opened this issue Apr 3, 2018 · 0 comments
Open

Different --silent use case #336

eviefp opened this issue Apr 3, 2018 · 0 comments

Comments

@eviefp
Copy link
Member

eviefp commented Apr 3, 2018

This is different from #261 and #290 due to the reasoning. I would like to be able to parse the result of pulp build -- --json-errors. So the idea would be to only silence anything that pulp adds on top of purs.

One example would be, if I'm doing a large refactor by updating a constructor or something. Most likely, that would yield quite a few errors which are quite verbose. I would much rather just see a simple list of file, module and line or something.

I'm sure there are other uses for parsing the compiler output for the whole project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant