Holger Just b228494d14 Raise a custom Rackstash::NotImplementedHereError instead of NotImplementedError ...

Using the core `NotInmplementedError` is not desireable since its
documentation includes:

> Note that if `fork` raises a `NotImplementedError`, then
> `respond_to?(:fork)` returns `false`.

Since we are responding to the method but still raise an error, our
usage of the exception does not fulfill its documentation.

A custom error instead of a default `NoMethodError` is still desireable
since it significantly helps with debugging. With a different Exception,
we make it clear that a method is expected to be there and just wasn't
implemented by a subclass as opposed to the caller just using an object
wrong and calling entirely unexpected methods on it.

2017-08-01 12:28:58 +02:00

..

rackstash

Raise a custom Rackstash::NotImplementedHereError instead of NotImplementedError

2017-08-01 12:28:58 +02:00

rackstash_spec.rb

Raise a custom Rackstash::NotImplementedHereError instead of NotImplementedError

2017-08-01 12:28:58 +02:00

spec_helper.rb

Use frozen string literals throughout the codebase in Ruby >= 2.3

2017-07-17 13:35:24 +02:00