Ryan Luker

> > Do you know if it is all files within your codebase or just a subset? > > Unfortunately, it appears not. I wrote a few unit tests to...

> I'll wait :) My VS Code extension experience is close to NIL. Thanks for update. No worries, I always like to at least present the option, as sometimes people...

@GitMensch Thanks for submitting an issue! Definitely seems like a useful addition, and the codebase is pretty setup for doing these changes when the config is initialized. https://github.com/ryanluker/vscode-coverage-gutters/blob/master/src/extension/config.ts Not sure...

> I've found a workaround after viewing some of the sample files in https://github.com/fschwaiger/cobertura-parse. > > Looks like the dotnet-compile doesn't include this:  > > `` tag. Once I...

@robross0606 Thanks for the ticket! Are you able to check out the extension logging and see if the extension is finding any coverage in the file paths you have specified?...

@robross0606 Interesting! I would have to rack my brain but I think the bottom coverage indicator always showed the current files covered lines. There definitely could be improvements here for...

@rginnow Thanks for the message! It is common that folks have incorrect file paths as they often have the IDE running in a different area then the code coverage generation...

@simplenotezy Thanks for the ticket! We have changed the default keybindings before as they usually come into conflict with different vscode defaults as they change over time. AFAIK you are...

> > @simplenotezy Thanks for the ticket! > > We have changed the default keybindings before as they usually come into conflict with different vscode defaults as they change over...

@Blu114455 👍🏻