Open BioPhoton opened 1 month ago
Should we close https://github.com/code-pushup/cli/issues/722? What happens in CI? Should the CVS server get considered in the desinge decision?
We don't print issues in the CLI output (it would be way too much info), so I don't see that there's anything to consider about CI.
CI jobs may produce the Markdown artifacts, but artifacts' content isn't viewable online anyway, you have to download the file and open it - probably in your IDE :grin: So local path links should still cover most use cases, I think.
The thought was driven by the fact that ppl could store the report in the repo or add it to a pr.
I started to elaborate it here #748
User story
As a user of the CLI I want to have click through experience for all actionable feedback a get from the audit issues.
At the moment the provided issues often show exactly where the error needs to get fixed, but a manual navigation to the line of code is required.
Example:
src/lib/index.ts
src/lib/index.ts
src/lib/index.ts
src/lib/index.ts
Acceptance criteria
../src/lib/index.ts
)../src/lib/index.ts#L9
)../src/lib/index.ts#L4-L8
)Folder:
Link in report:
[src/lib/index.ts](../src/lib/index.ts)
Example Report:
src/lib/index.ts
src/lib/index.ts
src/lib/index.ts
src/lib/index.ts
Implementation details
Essential logic and tests are present in the following PR, the over all configuration handling is not fully thought through.
https://github.com/code-pushup/cli/tree/add-link-to-local-filesystem-in-reports
Related Issues:
https://github.com/code-pushup/cli/issues/149