worked around Opal 0.11 singleton class issue

Author: catmando

ruby/hyper-model/lib/reactive_record/active_record/reactive_record/collection.rb

@@ -682,9 +682,13 @@ def method_missing(method, *args, &block)
       elsif ScopeDescription.find(@target_klass, "_#{method}")
         apply_scope("_#{method}", *args).first
       else
+        # create a subclass of the original target class that responds to all
+        # by returning our collection back
         fake_class = Class.new(@target_klass)
-        fake_class.singleton_class.attr_accessor :all
-        fake_class.all = self
+        fake_class.instance_variable_set("@all", self)
+        # Opal 0.11 does not handle overridding the original @target_klass
+        # with an accessor, so we define the accessor as a method.
+        fake_class.define_singleton_method(:all) { @all }
         fake_class.send(method, *args, &block)
       end
     end

ruby/hyper-model/spec/batch1/misc/where_and_class_method_delegation_spec.rb

@@ -42,6 +42,7 @@ def self.with_size(attr, size)
   end
 
   it "can take a hash like value" do
+    client_option raise_on_js_errors: :debug
     expect do
       ReactiveRecord.load { User.where(surname: "VanDuyn").pluck(:id, :first_name) }
     end.on_client_to eq User.where(surname: "VanDuyn").pluck(:id, :first_name)

ruby/hyper-model/spec/batch6/aaa_update_associations_spec.rb

@@ -138,14 +138,14 @@
   it "and a model in a belongs_to relationship can be destroyed" do
     expect do
       ReactiveRecord.load do
-        User.find_by_first_name("Jan").todo_items.collect { |item| item.itself }.first
-      end.then do | first |
-        first.destroy.then do |response|
+        User.find_by_first_name("Jan").todo_items.collect(&:itself).first
+      end.then do |first|
+        first.destroy.then do
           User.find_by_first_name("Jan").todo_items.all
         end.tap { @was_destroyed_already = first.destroyed? }
       end
-    end.on_client_to
-    # added to check that issue #119 got fixed.  Item is not
+    end.on_client_to be_empty
+    # added following to check that issue #119 got fixed.  Item is not
     # considered destroyed until we get the status back from server
     # that it was destroyed
     expect { @was_destroyed_already }.on_client_to be_falsy