From d79a0d52ddcf19074155ebedeca804811653fa38 Mon Sep 17 00:00:00 2001 From: Seth Vargo Date: Thu, 23 Oct 2014 13:42:02 -0400 Subject: [PATCH] Do not use Enumerable in Registry Calling methods like #first in Registry is misleading because it returns a different result than registry.get(registry.keys.first). --- lib/vagrant/registry.rb | 2 -- test/unit/vagrant/registry_test.rb | 4 ---- 2 files changed, 6 deletions(-) diff --git a/lib/vagrant/registry.rb b/lib/vagrant/registry.rb index bb8521f74..f3c86edec 100644 --- a/lib/vagrant/registry.rb +++ b/lib/vagrant/registry.rb @@ -4,8 +4,6 @@ module Vagrant # This allows certain components (such as guest systems, configuration # pieces, etc.) to be registered and queried, lazily. class Registry - include Enumerable - def initialize @items = {} @results_cache = {} diff --git a/test/unit/vagrant/registry_test.rb b/test/unit/vagrant/registry_test.rb index 12ccbec5c..f177a6a1c 100644 --- a/test/unit/vagrant/registry_test.rb +++ b/test/unit/vagrant/registry_test.rb @@ -3,10 +3,6 @@ require File.expand_path("../../base", __FILE__) describe Vagrant::Registry do let(:instance) { described_class.new } - it "should include enumerable" do - expect(instance).to be_a(Enumerable) - end - it "should return nil for nonexistent items" do expect(instance.get("foo")).to be_nil end