Skip to content
Commits on Jun 21, 2015
  1. Merge pull request #7 from gitter-badger/gitter-badge

    Add a Gitter chat badge to README.md
    committed Jun 21, 2015
  2. @gitter-badger

    Added Gitter badge

    gitter-badger committed Jun 21, 2015
Commits on Jan 9, 2015
  1. Added 2.2.0 to CI

    committed Jan 8, 2015
  2. Updated spreadsheet dependency

    spreadsheet had a broken patch version at 0.9.9, and pushed the fix as
    1.0.0. so much for semver. Argument here:
    
    zdavatz/spreadsheet#111
    committed Jan 8, 2015
Commits on Feb 13, 2014
  1. Merge branch 'master' of github.com:bspaulding/Sheets

    Conflicts:
    	Rakefile
    Bradley J. Spaulding committed Feb 13, 2014
  2. Bumped version to 1.2

    Bradley J. Spaulding committed Feb 13, 2014
  3. Removed unused rake tasks.

    Bradley J. Spaulding committed Feb 13, 2014
  4. Merge pull request #5 from dmtroyer/update_gems

    All gem dependencies are updated to the latest versions.
    committed Feb 12, 2014
  5. All gem dependencies are updated to the latest versions.

    Nokogiri supports Ruby >= 1.9.2, so support for 1.8.7 and ree support is dropped.
    David Troyer committed Feb 12, 2014
Commits on Feb 12, 2014
  1. Bumped version to 1.1.2

    Bradley J. Spaulding committed Feb 12, 2014
  2. Merge pull request #4 from bspaulding/improve-flay

    Extracted Sheets::Utilities.subclasses_in
    committed Feb 11, 2014
Commits on Feb 11, 2014
  1. Extracted Sheets::Utilities.subclasses_in

    Bradley J. Spaulding committed Feb 11, 2014
  2. Merge pull request #3 from bspaulding/refactor-nokogiri-parser

    Refactored nokogiri parser
    committed Feb 11, 2014
  3. Refactored NokogiriXlsxParser#value_for_cell

    Bradley J. Spaulding committed Feb 11, 2014
  4. Added a boolean cell type test for xlsx

    Bradley J. Spaulding committed Feb 11, 2014
  5. Added simplecov.

    Bradley J. Spaulding committed Feb 11, 2014
  6. Refactored NokogiriXlsxParser.

    Bradley J. Spaulding committed Feb 11, 2014
  7. Added ruby 2.0 and 2.1 to travis config.

    Bradley J. Spaulding committed Feb 11, 2014
  8. Added .ruby-version to .gitignore

    Bradley J. Spaulding committed Feb 11, 2014
  9. Locking down gem requirements for 1.8 ruby compatibility.

    Bradley J. Spaulding committed Feb 11, 2014
  10. Set notification email for travis.

    Bradley J. Spaulding committed Feb 11, 2014
  11. Added CodeClimate badge to README

    Bradley J. Spaulding committed Feb 11, 2014
Commits on Mar 26, 2013
  1. Cleaned trailing whitespace.

    Bradley J. Spaulding committed Mar 25, 2013
  2. Updated travis badge in README.md.

    Bradley J. Spaulding committed Mar 25, 2013
Commits on Oct 3, 2012
  1. Updated version to 1.1.1.

    committed Oct 3, 2012
  2. Merge pull request #1 from mnoble/load_worksheets_sequentially

    Don't rely on worksheet_id to match filename
    committed Oct 3, 2012
  3. @mnoble

    Don't rely on worksheet_id to match filename

    Excel worksheets get an id when they are created. When worksheets are
    removed, it seems as though id's are not reassigned, but their filenames
    are. For example:
    
      Worksheet (id 1) #=> xl/worksheets/sheet1.xml
      Worksheet (id 2) #=> xl/worksheets/sheet2.xml
      Worksheet (id 3) #=> xl/worksheets/sheet2.xml
    
    If you delete the second worksheet, the filenames change, but the ids do
    not, it seems. What you end up with is:
    
      Worksheet (id 1) #=> xl/worksheets/sheet1.xml
      Worksheet (id 3) #=> xl/worksheets/sheet2.xml
    
    The current XLSX parser assumes the filename of a worksheet contains
    its id. This is not the case for the example above.
    
    This change makes it load worksheets sequentually, from 1 to the number
    of worksheets, instead of id (which doesn't change). Assuming the
    worksheet filenames are changed when adding/removing worksheets, this
    should work.
    mnoble committed Oct 3, 2012
Commits on Nov 29, 2011
  1. Updated version for tag.

    committed Nov 29, 2011
  2. Updated README.

    committed Nov 29, 2011
Something went wrong with that request. Please try again.