…filer Conflicts: README Rakefile lib/flat_file.rb pkg/flat_filer-0.0.14.gem spec/flat_filer_spec.rb
When the :default option is used, if the model being mapped into is blank, and the flat filer record field is blank, the default value is mapped into the field on the model.
…rote specs to verify.
…abbing code from rails to support blank?
…r (bad flat filer).
was acting way too aggressively. So unless a field is supposed to be agressive (using field def option :aggressive => true) it defaults to being passive. Passive fields won't map into a model if the field is already set in the model.
Tests ajusted to test for this.
Because of something going on with ACE we thought that the formatters were not working. According to this test, it seems that they are. I'm going to run back to the ace codebase to see if I can determine what's going on. o Updated flat filer so that next_record can return a record in addition to taking a block for processing the record.
we were skipping every other line in a file when using each_record().
version 0.0.10. It broke many things.
o Testing now done with specs, removed references to old tests which didn't really work anyway. o Added the ability to have a map_in_proc attribute on a field definition. This option actually executes the logic to map a flat filer record value into a ruby object (model).
… method Changed typo so width will work on the class, and added an instance method to do the same thing as the class method. Added test, and release 0.0.8.
Added default value to line_number parameter on FlatFiler#create_record
put into 0.0.5.
from tangeis ticket 910.
o Added true tests based on Test::Unit o Added concept of filters and formatters o Added ability to add fields with blocks, or parameters (like migrations) o Added a decent compliment of rdoc documentation