vaadin / vaadin-text-field
95%
master: 96%

LAST BUILD BRANCH: v2.8.1
DEFAULT BRANCH: master
Repo Added
Files 7
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

LAST BUILD ON BRANCH fix/numberfield-step-validation
branch: fix/numberfield-step-validation
CHANGE BRANCH
x

2792

Pull #421

travis-ci

web-flow 
Adjust integer-field test

By setting the attribute manually instead of using reflectToAttribute,
the step value set as a string gets converted into a number.

I'd consider this to be a fix instead of a breaking thing, because the
property type is number.
Pull Request #421: fix: avoid using initial step in validation

269 of 289 branches covered (93.08%)

Branch coverage included in aggregate %.

5 of 5 new or added lines in 1 file covered. (100.0%)

408 of 420 relevant lines covered (97.14%)

1837.47 hits per line

Relevant lines Covered
420 RELEVANT LINES 408 COVERED LINES
1837.47 HITS PER LINE
Source Files on fix/numberfield-step-validation
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses

Recent builds

Builds Branch Commit Type Ran Committer Via Coverage
2792 fix/numberfield-step-validation Adjust integer-field test By setting the attribute manually instead of using reflectToAttribute, the step value set as a string gets converted into a number. I'd consider this to be a fix instead of a breaking thing, because the property type is... Pull #421 web-flow travis-ci pending completion  
2791 fix/numberfield-step-validation Adjust integer-field test By setting the attribute manually instead of using reflectToAttribute, the step value set as a string gets converted into a number. I'd consider this to be a fix instead of a breaking thing, because the property type is... push pekam travis-ci pending completion  
2782 fix/numberfield-step-validation Validate by step when set as attribute The only problem is that we can't detect when user has set step="1" (default value) as an attribute. In this case it won't validate by step (same as not setting step at all). Pull #421 web-flow travis-ci pending completion  
2783 fix/numberfield-step-validation Validate by step when set as attribute The only problem is that we can't detect when user has set step="1" (default value) as an attribute. In this case it won't validate by step (same as not setting step at all). push pekam travis-ci pending completion  
2745 fix/numberfield-step-validation fix: avoid using initial step in validation setting the min or max property should not trigger step-based validation fix #420 Pull #421 web-flow travis-ci pending completion  
2744 fix/numberfield-step-validation fix: avoid using initial step in validation setting the min or max property should not trigger step-based validation fix #420 push pekam travis-ci pending completion  
2743 fix/numberfield-step-validation fix: avoid using initial step in validation setting the min or max property should not trigger step-based validation fix #420 Pull #421 web-flow travis-ci pending completion  
2742 fix/numberfield-step-validation fix: avoid using initial step in validation setting the min or max property should not trigger step-based validation fix #420 push pekam travis-ci pending completion  
2741 fix/numberfield-step-validation fix: avoid using initial step in validation setting the min or max property should not trigger step-based validation fix #420 push pekam travis-ci pending completion  
See All Builds (1055)