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

bwillis / versioncake
99%
master: 20%

Build:
Build:
LAST BUILD BRANCH: github-actions
DEFAULT BRANCH: master
Repo Added 25 Mar 2013 12:57AM UTC
Files 4
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 feature-allow_flexible_routing_for_unsupported_versions
branch: feature-allow_flexible_routing_for_unsupported_versions
CHANGE BRANCH
x
Reset
  • feature-allow_flexible_routing_for_unsupported_versions
  • add-rails-5-2-specs
  • add-version-to-response
  • available-versions
  • bump-for-security-fixes
  • bump-versions
  • dependabot/bundler/actionpack-5.2.4.3
  • dependabot/bundler/actionview-5.2.4.1
  • dependabot/bundler/actionview-5.2.4.2
  • dependabot/bundler/activesupport-5.2.4.3
  • dependabot/bundler/rake-13.0.1
  • feature-configuration_refactoring
  • feature-date_versioning
  • feature-migrate_tool_from_v1_to_v2
  • feature-strategy_refactoring
  • feature-yml_testing_strategy
  • fix-build-failure
  • fix-rails-6-dep
  • fix-supported-version-numbers
  • fixing-bugs-with-missing-version
  • github-actions
  • master
  • rack-middleware-spike
  • rails-4.1-support
  • remove-legacy-ruby-rails-support
  • security-updates
  • set-version-not-working
  • support-missing-version-as-unversioned-template
  • support-rails-6
  • test-unit-to-rspec
  • update-dependencies
  • update-security-dependencies
  • upgrade-gems
  • upgrade-gems-a
  • use-memoized-lookup-context
  • v2.1
  • v2.2
  • v2.4
  • v2.5
  • v3.0
  • v3.1
  • v3.2
  • v3.3
  • v3.4
  • v4.0
  • v4.0.1
  • v4.0.2
  • versioned-middleware

pending completion
138

push

travis-ci

bwillis
Raise a specific exception on unsupported version

When a version is found that is no longer supported, or never was
supported, an application may want to handle this differently.
Previously generic routing error exceptions were raised and the
exception message stated no match or version is deprecated. Having the
same exception made it difficult to determine if it was not supported
or invalid, also the unsupported routing error erroneously contained
the word deprecated.

The new approach is to raise a new typed exception when the version is
not supported. It will include the versioned request as part of the
exception to allow inspection in an error handler.

This should resolve the issue #24.

489 of 493 relevant lines covered (99.19%)

81.04 hits per line

Relevant lines Covered
Build:
Build:
493 RELEVANT LINES 489 COVERED LINES
81.04 HITS PER LINE
Source Files on feature-allow_flexible_routing_for_unsupported_versions
  • List 0
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line

Recent builds

Builds Branch Commit Type Ran Committer Via Coverage
138 feature-allow_flexible_routing_for_unsupported_versions Raise a specific exception on unsupported version When a version is found that is no longer supported, or never was supported, an application may want to handle this differently. Previously generic routing error exceptions were raised and the exc... push 01 Mar 2014 11:17PM UTC bwillis travis-ci pending completion  
137 feature-allow_flexible_routing_for_unsupported_versions Raise a specific exception on unsupported version When a version is found that is no longer supported, or never was supported, an application may want to handle this differently. Previously generic routing error exceptions were raised and the exc... push 01 Mar 2014 11:14PM UTC bwillis travis-ci pending completion  
See All Builds (305)
  • Repo on GitHub
  • CI Project
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

© 2025 Coveralls, Inc