ability to capture (non-fixable) eslint errors/warnings? about prettier-eslint HOT 5 CLOSED

PR welcome

from prettier-eslint.

Stale issue

from prettier-eslint.

Oh, sorry I let this get stale. Working on a PR now. As far as I can see, the interface of format cannot be changed: it takes a code string and a path name where that code nominally resides, and returns a code string. So the plan I am working on in the PR is to add another export, tentatively named analyze, which takes the same arguments but returns a simple object with keys output whose value is the same string as format currently produces, and messages with all of the messages produced in the generation of output, if any. If that doesn't sound like a good plan or you feel the naming should be different, please advise.

from prettier-eslint.

Confused why this is closed before #827 is merged?

from prettier-eslint.

With #827 closed (what else can I do to help fix this?), could this issue be re-opened? It has not been resolved, and it was judged "PR welcome" initially. My apologies for the long period between that invitation and the PR I submitted, but please let me know if there is anything I can do to move toward a solution for this issue. Thanks!

from prettier-eslint.