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

Silence report if containing no findings #1860

Merged
merged 1 commit into from
Aug 31, 2019
Merged

Silence report if containing no findings #1860

merged 1 commit into from
Aug 31, 2019

Conversation

schalkms
Copy link
Member

The FindingsReport should not produce any output if there are no
code smells at all.
This fixes #1854

The `FindingsReport` should not produce any output if there are no
code smells at all.
This fixes #1854
@schalkms schalkms merged commit 82f5e06 into detekt:master Aug 31, 2019
@schalkms schalkms deleted the silent-FindingsReport branch August 31, 2019 10:57
sowmyav24 pushed a commit to sowmyav24/detekt that referenced this pull request Aug 31, 2019
The `FindingsReport` should not produce any output if there are no
code smells at all.
This fixes detekt#1854
sowmyav24 pushed a commit to sowmyav24/detekt that referenced this pull request Aug 31, 2019
The `FindingsReport` should not produce any output if there are no
code smells at all.
This fixes detekt#1854
sowmyav24 pushed a commit to sowmyav24/detekt that referenced this pull request Aug 31, 2019
The `FindingsReport` should not produce any output if there are no
code smells at all.
This fixes detekt#1854
sowmyav24 pushed a commit to sowmyav24/detekt that referenced this pull request Aug 31, 2019
The `FindingsReport` should not produce any output if there are no
code smells at all.
This fixes detekt#1854
sowmyav24 pushed a commit to sowmyav24/detekt that referenced this pull request Aug 31, 2019
The `FindingsReport` should not produce any output if there are no
code smells at all.
This fixes detekt#1854
sowmyav24 pushed a commit to sowmyav24/detekt that referenced this pull request Aug 31, 2019
The `FindingsReport` should not produce any output if there are no
code smells at all.
This fixes detekt#1854
sowmyav24 pushed a commit to sowmyav24/detekt that referenced this pull request Aug 31, 2019
The `FindingsReport` should not produce any output if there are no
code smells at all.
This fixes detekt#1854
sowmyav24 pushed a commit to sowmyav24/detekt that referenced this pull request Aug 31, 2019
The `FindingsReport` should not produce any output if there are no
code smells at all.
This fixes detekt#1854
sowmyav24 pushed a commit to sowmyav24/detekt that referenced this pull request Aug 31, 2019
The `FindingsReport` should not produce any output if there are no
code smells at all.
This fixes detekt#1854
sowmyav24 pushed a commit to sowmyav24/detekt that referenced this pull request Sep 2, 2019
The `FindingsReport` should not produce any output if there are no
code smells at all.
This fixes detekt#1854
@arturbosch arturbosch added this to the 1.0.2 milestone Sep 6, 2019
@arturbosch arturbosch modified the milestones: 1.0.2, 1.1.0 Sep 17, 2019
smyachenkov pushed a commit to smyachenkov/detekt that referenced this pull request Dec 9, 2019
The `FindingsReport` should not produce any output if there are no
code smells at all.
This fixes detekt#1854
smyachenkov pushed a commit to smyachenkov/detekt that referenced this pull request Dec 9, 2019
The `FindingsReport` should not produce any output if there are no
code smells at all.
This fixes detekt#1854
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.

Silent mode still produces output
2 participants