bwillis / versioncake

99%

master: 20%

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

Build # 138

Build Type

push

travis-ci

Committed by bwillis

Commit Message

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.

Run Details

489 of 493 relevant lines covered (99.19%)

81.04 hits per line