search

ryanluker / vscode-coverage-gutters

Display test coverage generated by lcov and xml - works with many languages
https://marketplace.visualstudio.com/items?itemName=ryanluker.vscode-coverage-gutters
MIT License
460 stars 88 forks source link

monorepo support? #276

Closed shaunc closed 3 years ago

shaunc commented 3 years ago

Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

The project doesn't seem to be working for me on first install. I suspect (given there is only one "cov.xml" in the options) that it does not support monorepos. (If this is incorrect, I'll be happy to learn how to setup.)

Describe the solution you'd like A clear and concise description of what you want to happen.

I would like to be able to use with a monorepo -- possibly containing packages in several different languages. Ideally it would "just work" -- searching for cov.xml in subdirectories. Optionally, include/exclude paths for this search would make sense.

Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.

I haven't thought of a good workaround yet.

Additional context Add any other context or screenshots about the feature request here.

ryanluker commented 3 years ago

@shaunc thanks for submitting an issue! you definitely should be able to use multiple coverage files 🤔 within the same workspace. https://github.com/ryanluker/vscode-coverage-gutters/blob/master/test/extension.test.ts#L216 https://github.com/ryanluker/vscode-coverage-gutters/blob/master/package.json#L142-L151

Can you load the example workspace and see if you can see coverage for both the node and java projects if you use the watch feature? You might need to up the settings from the 2nd link above that lets you manually pick coverage file names.

Let me know how that ends up working for yah!

shaunc commented 3 years ago

OK -- got it to work. Unfortunately, I'm not sure where I screwed up. I think I over-thought it when it didn't work initially, and snarled up the settings, when perhaps I should have just reloaded the window. :)

Thanks!