They allow the user to override only the min or max value without having to
know the default value for the other end of the range.


On Thu, Dec 19, 2013 at 3:54 AM, Daniel Spilker <notifications@github.com>wrote:

> In
> job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/publisher/EmmaContext.groovy:
>
> > @@ -0,0 +1,77 @@
> > +package javaposse.jobdsl.dsl.helpers.publisher
> > +
> > +import javaposse.jobdsl.dsl.helpers.Context
> > +
> > +class EmmaContext implements Context {
> > +
> > +    IntRange classThreshold = 0..100
> > +    IntRange methodThreshold = 0..70
> > +    IntRange blockThreshold = 0..80
> > +    IntRange lineThreshold = 0..80
> > +    IntRange conditionThreshold = 0..<1
> > +
> > +    void minClass(int min) {
>
> What's the benefit of having the min/max methods? The IntRange syntax is
> short and precise.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/jenkinsci/job-dsl-plugin/pull/117/files#r8463520>
> .
>