search

aconrad / pycobertura

A code coverage diff tool for Cobertura reports
MIT License
114 stars 39 forks source link

Pycobertura diff command only supports text and html output format? #143

Closed chixiangzhou closed 2 years ago

chixiangzhou commented 2 years ago

Problem: I was trying to generate a yaml output using pycobertura diff command. But it threw an error and implies that only text and html are supported. See the screenshot below: image

The README shows yaml, json, and other format are also supported.

The version of pycobertura I'm currently using is 2.1.0. See the screenshot below: image

Did I miss anything here?

aconrad commented 2 years ago

We haven't released that feature yet. It will be part of v3. You'd have to use the master branch instead of the python package in the meantime.

chixiangzhou commented 2 years ago

I see. Do you know when will that feature be released?

aconrad commented 2 years ago

@gro1m has been helping a lot lately, we're trying to go through some of the issues and see if we can fix some low-hanging fruit and add new features. But on my side, time is my main constraint, life keeps me pretty busy and yet I try to respond to incoming requests in a somewhat timely manner. 😅

I should do a better job at identifying which of those are meant to be in 3.0. Maybe we should use a "3.0" label or something so we can better keep track of our progress...

The changes you suggested in #142 would be nice additions, too. If you want to help with those (e.g. consider that previously non-exist files are "100%" covered, or show before/after columns in the summary table). We can start by capturing this work in separate tickets and then we can discuss how to move forward. Thoughts?

chixiangzhou commented 2 years ago

The changes you suggested in https://github.com/aconrad/pycobertura/issues/142 would be nice additions, too. If you want to help with those (e.g. consider that previously non-exist files are "100%" covered, or show before/after columns in the summary table). We can start by capturing this work in separate tickets and then we can discuss how to move forward. Thoughts?

Sure. I'll capture this work in a separate ticket. Like i mentioned in #142 , I'll try my best to help with this enhancement, but it might take a bit of time for me. Just wanted to set the right expectation here. 😅

chixiangzhou commented 2 years ago

I filed two tickets #144 and #145 to capture the work.

chixiangzhou commented 2 years ago

Closing this ticket #143, as I think you answered my question.