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

Less verbose creation of ScalastyleConfiguration #223

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

andrelfpinto
Copy link

Decreasing the verboseness of ScalastyleConfiguration creation can be useful, for example, to the substitution of the process of parsing the XML configuration file by the manual creation of the object itself in Scala (which is "type-safer") in the SBT plugin.
This adds default parameters to ScalastyleConfiguration and a new apply to ConfigurationChecker that uses a ClassTag to get the class name.

@codecov-io
Copy link

Current coverage is 87.10% (diff: 0.00%)

No coverage report found for master at 129957e.

Powered by Codecov. Last update 129957e...e46758c

@codecov-io
Copy link

codecov-io commented Oct 9, 2016

Codecov Report

Merging #223 into master will not change coverage.
The diff coverage is 0%.

Impacted file tree graph

@@          Coverage Diff          @@
##           master   #223   +/-   ##
=====================================
  Coverage       0%     0%           
=====================================
  Files          62     62           
  Lines        1495   1496    +1     
  Branches      146    148    +2     
=====================================
- Misses       1495   1496    +1
Impacted Files Coverage Δ
...scala/org/scalastyle/ScalastyleConfiguration.scala 0% <0%> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5c4bb3e...64c0184. Read the comment docs.

Decreasing the verboseness of `ScalastyleConfiguration` creation can be useful,
for example, to the substitution of the process of parsing the XML
configuration file by the manual creation of the object itself in Scala (which
is "type-safer") in the SBT plugin.
This adds default parameters to `ScalastyleConfiguration` and a new `apply` to
`ConfigurationChecker` that uses a `ClassTag` to get the class name.
@andrelfpinto
Copy link
Author

Hi, @matthewfarwell, is this PR reasonable?

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.

None yet

2 participants