fixed unparser issue

Author: catmando

change-log.md

@@ -4,6 +4,14 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## 1.4alpha - 2019-02-15
+### Security
++ [#117](https://github.com/hyperstack-org/hyperstack/issues/117) Finder methods will return nil instead of raising access violations.
+
+### Added
++ [#120](https://github.com/hyperstack-org/hyperstack/issues/120) Alias `ActiveRecord::Base#new_record?` to `#new?`.
++ [#112](https://github.com/hyperstack-org/hyperstack/issues/112) Add `:init` param to `INPUT`, `SELECT`, and `TEXTAREA` tags.
+
 ## 1.3alpha - 2019-01-16
 ### Security  
 + [#102](https://github.com/hyperstack-org/hyperstack/issues/102) Security hole in find_record method filled.

ruby/hyper-model/spec/batch1/column_types/column_type_spec.rb

@@ -239,11 +239,21 @@ class DefaultTest < ActiveRecord::Base
   end
 
   it 'converts a 0, "false" false and nil to a boolean false, everything else is true' do
+    # there is a bug someplace (unparser probably) that is is treating the empty array as nil
+    # but ONLY if it is the normal ruby block (not a string) AND if you use a normal arg
+    # instead of *args. In other words put that same expression in a string and change
+    # *args/args.first to plain old arg and it works fine.
     expect_evaluate_ruby do
+      [0, 'false', false, nil, 'hi', 17, [], true].collect do |*args|
+        TypeTest.new(boolean: args.first).boolean
+      end
+    end.to eq([false, false, false, false, true, true, true, true])
+
+    expect_evaluate_ruby("
       [0, 'false', false, nil, 'hi', 17, [], true].collect do |val|
         TypeTest.new(boolean: val).boolean
       end
-    end.to eq([false, false, false, false, true, true, true, true])
+    ").to eq([false, false, false, false, true, true, true, true])
     check_errors
   end