Skip to content
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

coverage: default prefix stripping to workspace root #1428

Merged
merged 3 commits into from
Jan 15, 2025

Conversation

lsegal
Copy link
Member

@lsegal lsegal commented Jan 15, 2025

Also: various linter fixes in the qlty-coverage package

Also: various linter fixes in the qlty-coverage package
@lsegal lsegal requested a review from a team January 15, 2025 01:39
@lsegal lsegal self-assigned this Jan 15, 2025
Copy link
Contributor

qltysh bot commented Jan 15, 2025

The code coverage on the diff in this pull request is 50.0%

Drilldown
Path File Coverage Δ
qlty-config/src/library.rs -0.5
qlty-cli/src/commands/coverage/publish.rs 0.8
qlty-coverage/src/print.rs 0.0
qlty-coverage/src/transformer.rs -10.4
qlty-config/src/workspace.rs 1.3
qlty-coverage/src/publish/planner.rs -3.2

@marschattha
Copy link
Member

marschattha commented Jan 15, 2025

If I am reading this correctly, won't it sort of undo #1194, i-e the project will need to have a qlty.toml for coverage to work?

Updating tests like #1429 would also prevent the regression.

@lsegal
Copy link
Member Author

lsegal commented Jan 15, 2025

I think it could make sense to lower the burden to assert_within_git_directory, especially for cloud builds.

@lsegal lsegal merged commit 470e0ad into main Jan 15, 2025
11 checks passed
@lsegal lsegal deleted the ls/coverage-fix-run-from-subdir branch January 15, 2025 19:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants