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

Analysis report is not being written to a file #156

Closed
nishiths23 opened this issue Nov 12, 2024 · 3 comments · Fixed by #161
Closed

Analysis report is not being written to a file #156

nishiths23 opened this issue Nov 12, 2024 · 3 comments · Fixed by #161
Assignees
Labels
Error Report something not working

Comments

@nishiths23
Copy link

Describe the error
dart run dart_code_linter:metrics analyze --reporter=json --json-path="./report.json" lib is not generating a report file

How ​​to replicate the bug
Step by step to reproduce the error:

  1. run dart run dart_code_linter:metrics analyze --reporter=json --json-path="./report.json" lib

Runtime environment

  • OS: Mac
  • Version: 1.1.5
@nishiths23 nishiths23 added the Error Report something not working label Nov 12, 2024

Assign to review: @santitigaga @ajtortolero

@app-toolkit-opensource-innersource app-toolkit-opensource-innersource bot added the Review/Pending Initial stage of the issue to evaluate its approval label Nov 12, 2024
@santitigaga santitigaga self-assigned this Nov 18, 2024
@santitigaga santitigaga removed the Review/Pending Initial stage of the issue to evaluate its approval label Nov 18, 2024
@santitigaga
Copy link
Contributor

@nishiths23 you are right I fix that in the next PR

@santitigaga
Copy link
Contributor

The problem occurs when the report has issues and the command don't have the flags --no-fatal-style, --no-fatal-warnings, --no-fatal-performance
But don't worry, it is fixed in version 1.2.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Error Report something not working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants