Different languages about coverage HOT 5 CLOSED

The module was renamed to https://github.com/jcubic/coverage.el and it now support php and JavaScript.

Since your package is on melpa you may consider grabbing my code and integrating it with the package.

from coverage.

Hi @jcubic I'm currently using this only for Ruby myself but will spend a bit of time looking into what it would take to support other languages. Thanks for opening the issue.

from coverage.

Python would be very useful, too. There's a Python fork of coverage-mode by @Bogdanp.

Possible approach:

• coverage/get-results-for-file is the backend, needs to have one implementation per target language. Could extract those from the forks posted here?
• Looking at the value of major-mode (for the current buffer), or the file extension (for an arbitrary file), should help detect which backend to invoke.

Integrating these forks into the official package would have the added advantage of easy install in Spacemacs for users of one of the alternative backends. Right now, to get one of them dotspacemacs-additional-packages needs something like (coverage :location (recipe :fetcher github :repo "someuser/coverage")), but for the official package on MELPA, just the package name is enough.

Of course, having all backends in the same package would also help users who need more than one language. :)

from coverage.

Hi @Technologicat, thanks for the suggestion 💯. I appreciate the input.

I will find some time in the next few weeks to take a look at this.

from coverage.

Sorry I haven't had time to look into this, I'm happy to accept pull requests but as I'm not using coverage for anything except Ruby at the moment it's a lot of work to set up projects to be able to test & develop this.

from coverage.