-
Notifications
You must be signed in to change notification settings - Fork 15
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
feat(plugin-doc-coverage): add doc-coverage-plugin to analyze documentation in ts/js projects #896
base: main
Are you sure you want to change the base?
Conversation
Code PushUp😟 Code PushUp report has regressed – compared target commit c219602 with source commit c219602. 🏷️ Categories👎 1 group regressed, 👎 5 audits regressed, 12 audits changed without impacting score🗃️ Groups
16 other groups are unchanged. 🛡️ Audits571 other audits are unchanged. |
…anced and some code improved
…ls. Solid version working
…te unit test for runner file
… unused dependency, new test
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.
Thanks for adding the tests.
Last thing I found was a outdated readme. After that we are good to go.
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.
WONDERFUL!
cc @vmasek and @matejchalk
@aramirezj thank you for putting this plugin together, we did discuss it on refinement today and we are exited to adopt it as one of the plugins that should live in this monorepo (there are plugins that we purposely do not maintain here as they do not meet the JS/TS tech stack). We are also looking forward to setup automated docs generation, so it makes even more sense to start tracking it with plugin. There are some things we need to figure out before we merge, mainly related to testing. We are thinking if there should already be a simple e2e tests similar to for the ESLint e2e exaple, is it something you'd also like to contribute? |
I am glad to hear that! And sure! I will work into that ^^ |
nodesCount: 1, | ||
issues: [ | ||
{ | ||
file: expect.stringContaining('classes-coverage'), |
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.
file: expect.stringContaining('classes-coverage'), | |
file: expect.stringContaining('classes-coverage.ts'), |
To make sure it is at the end of the file, and not a different file with same path segment.
This is applicable to multiple places.
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'd even say it could be stringEndingWith('classes-coverage.ts')
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 have added expect.stringMatching(/properties-coverage\.ts$/)
that it should do the trick
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.
@aramirezj with the latest merge we have OS agnostic path helpers in the codebase:
https://github.com/code-pushup/cli/blob/main/testing/test-setup/src/lib/extend/path.matcher.unit.test.ts
Let's use them.
This PR includes:
Closes #908
Report Summary
Overview of Audit Groups, Audit Counts, and Diagnostic Issue Types.
classes-coverage
,methods-coverage
,functions-coverage
,interfaces-coverage
,variables-coverage
,properties-coverage
,types-coverage
,enums-coverage