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

Document '-paths-for-coverage.txt' for code coverage #10857

Open
d-haxton opened this issue Feb 25, 2020 · 0 comments
Open

Document '-paths-for-coverage.txt' for code coverage #10857

d-haxton opened this issue Feb 25, 2020 · 0 comments
Labels
coverage help wanted Someone outside the Bazel team could own this P3 We're not considering working on this, but happy to review a PR. (No assignee) team-Documentation Documentation improvements that cannot be directly linked to other team labels team-Rules-Server Issues for serverside rules included with Bazel type: documentation (cleanup)

Comments

@d-haxton
Copy link

d-haxton commented Feb 25, 2020

Description of the problem / feature request:

There is no documentation for -paths-for-coverage.txt.

Feature requests: what underlying problem are you trying to solve with this feature?

In the process of using this 'feature' in bazelbuild/rules_scala#1006 we just want to get some level of guarentee that this is not a hack and won't be broken anytime in the foreseeable future (or at least some level of transition plan to an alternative)

For reference the two places where this matters to us are:

} else if (jarEntryName.endsWith("-paths-for-coverage.txt")) {

For parsing.


For using the set to find the source file.

@jin jin added coverage team-Rules-Server Issues for serverside rules included with Bazel untriaged labels Feb 28, 2020
@lberki lberki added P3 We're not considering working on this, but happy to review a PR. (No assignee) type: documentation (cleanup) and removed untriaged labels Nov 18, 2020
@keertk keertk added the team-Documentation Documentation improvements that cannot be directly linked to other team labels label Jan 10, 2023
@keertk keertk added the help wanted Someone outside the Bazel team could own this label Jan 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
coverage help wanted Someone outside the Bazel team could own this P3 We're not considering working on this, but happy to review a PR. (No assignee) team-Documentation Documentation improvements that cannot be directly linked to other team labels team-Rules-Server Issues for serverside rules included with Bazel type: documentation (cleanup)
Projects
None yet
Development

No branches or pull requests

4 participants