Be more specific about the lookup of an Ollie::Base subclass. #2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
On line 27 of checker.rb, Ollie does a lookup of the class within the Ollie namespace to instantiate the checker for the key given. It fails in cases where the new class isn't loaded quickly enough to be chosen by the call to
.const_get
.To illustrate this, consider a Rails app using Redis. We're interested in fetching some info, so we write an
Ollie::Redis
class whichThe
Redis
class is defined on the mainObject
namespace. If the lookup occurs before theOllie::Redis
class I've defined is loaded, then I Ollie tries to instantiate a newRedis
object, because.const_get
is called beforeOllie::Redis
is loaded.This fix forces the key to be loaded from the
Ollie
namespace as the README prescribes.