You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I looked for other suggestions for such a feature and did not find one. Frankly, I'm surprised there isn't one.
Admittedly, I'm pretty new to coverage reports but it seems to me that most tools store the lcov formatted output in a predictable location coverage/lcov.info. It would be swell if coveralls automatically found that file and did the right thing without requiring me to pipe the file into the stdin of coveralls.
I recognize that this probably can't be as simple as just running coveralls without any arguments as it looks difficult to me to detect if stdin is provided or not. Could use a timeout to detect no stdin and then go look for the file...
Adding a simple flag like --find would be one way to differentiate the use cases.
We could also or alternatively add a second argument that specifies the lcov file to load specifically. This could even be differentiated from the existing argument by testing if the argument is a file vs a folder.
This would help Windows users tremendously as cat is often missing and | often doesn't work on Windows systems. I recognize that there is a simple solution that works for Linux and Windows of using stdin redirection but I still feel automatically finding lcov data or passing it as an argument and using it would be easier.
Since this library doesn't seem to be supported anymore I fix a bunch of things on a fork if you want to check it out and are still pulling the library into your packages: https://github.com/jtwebman/coveralls-next I kind of agree this would be a good idea. I would be willing to add it to the fork.
I looked for other suggestions for such a feature and did not find one. Frankly, I'm surprised there isn't one.
Admittedly, I'm pretty new to coverage reports but it seems to me that most tools store the lcov formatted output in a predictable location
coverage/lcov.info
. It would be swell if coveralls automatically found that file and did the right thing without requiring me to pipe the file into the stdin ofcoveralls
.I recognize that this probably can't be as simple as just running coveralls without any arguments as it looks difficult to me to detect if stdin is provided or not. Could use a timeout to detect no stdin and then go look for the file...
Adding a simple flag like
--find
would be one way to differentiate the use cases.We could also or alternatively add a second argument that specifies the lcov file to load specifically. This could even be differentiated from the existing argument by testing if the argument is a file vs a folder.
This would help Windows users tremendously as
cat
is often missing and|
often doesn't work on Windows systems. I recognize that there is a simple solution that works for Linux and Windows of using stdin redirection but I still feel automatically finding lcov data or passing it as an argument and using it would be easier.It might also directly help with issues like #150
The text was updated successfully, but these errors were encountered: