Given that the Resolver#key? method existed, I'm adding a mechanism to
inspect the container. I envision that this inspection is helpful from
a configuration validation and visualization stand-point. I am looking
to assert that my container has a handful of registrations so I can
begin writing further interface documentation for those dependencies.
Closes #12
Switching from fail to raise
@a59553e71a8f3f663c1e58368c566115ee41f024
As of Rubocop 0.38.0 raise is preferred over fail (see
bbatsov/rubocop#2732 for more discussion). So this commit brings
dry-container in line with the "standard" style enforcement of
Rubocop.
Adding Resolver#keys method
@906c0febd568f8d50260552a11cc9b03cfbe18c7
Given that the Resolver#key? method existed, I'm adding a mechanism to inspect the container. I envision that this inspection is helpful from a configuration validation and visualization stand-point. I am looking to assert that my container has a handful of registrations so I can begin writing further interface documentation for those dependencies.
Closes #12
Switching from fail to raise
@a59553e71a8f3f663c1e58368c566115ee41f024
As of Rubocop 0.38.0 raise is preferred over fail (see bbatsov/rubocop#2732 for more discussion). So this commit brings dry-container in line with the "standard" style enforcement of Rubocop.