-
Notifications
You must be signed in to change notification settings - Fork 392
Relative paths lcov #1004
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Relative paths lcov #1004
Conversation
…nto helper class (coverlet-coverage#263) Refactored functions to determine base paths from CoberturaReporter into helper class
…in report (coverlet-coverage#263) Updated LcovReporter to include only relative paths for source files in report
…into relative-paths-lcov
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@phaniva please sign the CLA. I'll take a look asap |
|
@MarcoRossignoli I have signed the CLA. Not sure if you received a notification automatically |
|
@phaniva yep I see, bit busy this period, I'll take a look asap. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like the idea, we can simplify and simply add a base class with this two helpers.
Sorry for the delay.
|
|
||
| namespace Coverlet.Core.Helpers | ||
| { | ||
| internal class FilePathHelper : IFilePathHelper |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that extract a service is too much for a path helper...I mean we won't inject different implementation there are no different way to get that path from file system.
Should be enough add a new base class abstract ReporterBase and add this two method as protected and inherit the reporter that needs this logic.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So only the reporter classes that need this behavior will inherit from ReporterBase and rest of them will continue to implement IReporter?
Why not inherit every reporter class from ReporterBase to keep things consistent?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok I won't oppose, the important things is that we have less code as possible to maintain, let's go for base class inherited by reporters
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool. I am going to close this pr and open a new one with base class design.
Here is the new pr.
#1120
Please review this design to see if it addresses the requirement. I changed it so that we can enable relative directory option for all report formats but only changed it for lcov for now.