• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

ruby-grape / grape / 3022 / 6
97%
master: 97%

Build:
DEFAULT BRANCH: master
Ran 14 Jul 2017 01:03PM UTC
Files 145
Run time 5s
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

14 Jul 2017 12:56PM UTC coverage: 98.901% (+0.002%) from 98.899%
2.4.1, gemfiles/rails_5.gemfile

push

travis-ci

dblock
[Bugfix] Handle deeply-nested dependent params (#1661)

* Repro issue #1659

* [Fix] Handle deeply-nested dependencies with `given`.

Behind the scenes, each call to `requires` or other params DSL method
pushes an entry onto a flat list of validators. The nesting structure
that your parameters can take on is tracked as an up-tree separately
on each scope, but that relationship isn't used to traverse the validations.
So, when I moved the dependency checking out of `should_validate?` and into
the actual validation, the `given` dependency stopped taking effect after
you nested parameters more than one level deep underneath.

To restore the behavior, I made the validation check recursively upwards
to see if it should or should not validate that scope.

* Add changelog entry.

11339 of 11465 relevant lines covered (98.9%)

28.25 hits per line

Source Files on job 3022.6 (2.4.1, gemfiles/rails_5.gemfile)
  • Tree
  • List 0
  • Changed 17
  • Source Changed 1
  • Coverage Changed 17
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 3022
  • Travis Job 3022.6
  • a284f24c on github
  • Prev Job for 2.4.1, gemfiles/rails_5.gemfile on master (#3015.6)
  • Next Job for 2.4.1, gemfiles/rails_5.gemfile on master (#3026.6)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc