-
Notifications
You must be signed in to change notification settings - Fork 0
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
Some reports are not generating #15
Comments
Hello, thank you so much for your feedback. Can you give me more details about your project structure? thank you :) |
actually i have a src folder which contains some.ts files and .spec.ts files where i want to execute .ts files and exclude .spec.ts so there is no exclude feature to do this with in the lib, what i am doing, i create a temp-src folder which having only .ts files and then i provide this folder to the code-health-meter cli
even providing only src folder without doing alterations, getting same output |
Tests files are excluded by default to avoid excluding known patterns: Then, can I have a screenshot of how your folder is organized to emulate the case on my side. I tried to execute the same script as you but I can got reports: Thank you :) |
here it is reproducible example
.spec.ts and e2e.ts also very common extensions to exclude or better to give power with include or exclude flag for users update: if i provide path second level like |
Thank you for the different information, I'll come back to you soon :) |
I did not have access to your sandbox "Devbox not found". Can you give me the public link ? thank you! |
ohh, ok give me mint |
what about this link |
It's working, perfect! |
ok, cool but still not generating code duplication reports in the reproducible example, does any OS related issues, currently i have macos using for this generation and do not see this reports at all example shows duplication audit where does not show it in my machine but again this is great work and great lib that no other lib generating this much of metrics (tested couple of libs) |
I also use macos. I'll give you a version with error console enabled, to be able to identify the issues. I'll come back soon to you. Thank you for your patience :) |
Can you run the command and paste all logs here please? thank you |
here is logs from my complex project |
Aha, I have some valuables logs: �[32minfo�[39m: [CodeCouplingAuditor - startAudit] error: Graphviz could not be found. Ensure that "gvpr" is in your $PATH. Error: spawn gvpr ENOENT This is needed to visualize graph, I should update the document. To install in macos:
And this error: �[32minfo�[39m: [CodeDuplicationAuditor - inspectDirectory] execSync error: spawnSync /bin/sh ENOBUFS I should update the code as follow: https://github.com/helabenkhalfallah/code-health-meter/blob/main/src/kernel/duplication/CodeDuplicationAuditor.js#L68 I'll work on these update and come back to you soon :) :) |
found another small issue, by providing --outputDir to the command, process get deleted existing files before creating new files which is not good, keep all files inside outputDir, just create new files may be seems issue here |
Hello I published a new version |
Thx for the fix, unfortunately this new version keep on hanging at middle and does not exit the process, need to look why whereas tested npx with 2.0.0 version and works like before |
Thank you so much for your feedback, should I use the same project to reproduce? can you give me more information about your:
Thank you :) |
thx for the quick reply, i can not reproduce it here My CI Pipeline broken first then checked in my local setup seems more related to my project where it is Mac Os process hangs at this step but reports were generated until codeCoupling, seems hangs at code duplication audit process I will need to check more and give you logs soon |
I am testing this lib to get some metrics (great lib that generating different metrics) but some reports were not generated like code-duplication dashboard and code-coupling etc..
is there any reason that do not get some other folders
The text was updated successfully, but these errors were encountered: