All Versions
70
Latest Version
Avg Release Cycle
70 days
Latest Release
1087 days ago

Changelog History
Page 5

  • v2.3.0 Changes

    April 09, 2016

  • v2.2.0 Changes

    March 23, 2016

  • v2.1.0 Changes

    January 27, 2016
    • 🔄 Changed how text elements are parsed - instead of string concatenation, they're now added as first class TextElement instances.
      • This fixes the problem with mixed text/XML in issue 33.

  • v2.0.4 Changes

    November 13, 2015
    • ➕ Add explicit watchOS and tvOS targets to the project for better Carthage support

  • v2.0.3 Changes

    October 25, 2015
    • ➕ Added support for Carthage builds with bitcode
    • ⬆️ Bumped to xcode7.1 usage of Quick and Nimble

  • v2.0.2 Changes

    October 21, 2015
    • ➕ Added tvOS deployment target for CocoaPods and tvOS support

  • v2.0.1 Changes

    September 22, 2015
    • ➕ Added watchos deployment target for CocoaPods and watchOS support

  • v2.0.0 Changes

    September 16, 2015
    • ➕ Added Swift 2.0 / Xcode 7.0 support
      • While API parity should exist between v1 and v2, the library attempts to support the new error handling support in Swift 2.0 when you call the byIndex/byKey methods respectively (the subscript methods don't currently support throwing exceptions).
      • Note that the existing subscript methods can still be used, though.
    • 🔄 Changed .Error to .XMLError - this is part of handling Swift 2.0's new error handling support.
      • The prior .Error case received an NSError type whereas the new .XMLError case receives an Error which is an ErrorType with various cases to show which part of the parsing threw an error (i.e. Attribute, AttributeValue, Key, Index, or Init).

  • v1.1.1 Changes

    August 03, 2015
    • 🔄 Changed code signing options on the project to not code sign for OSX and to target iOS Developer.

  • v1.1.0 Changes

    June 20, 2015
    • ➕ Add configure method off of SWXMLHash to allow for setting variable number of options.
      • At this time, the only options are shouldProcessLazily and shouldProcessNamespaces.
      • shouldProcessLazily provides the same parsing as directly calling lazy. I'm considering deprecating the top-level lazy method in favor of having it be set in configure, but I'm open to suggestions here (as well as to suggestions regarding the configure method in general).
      • shouldProcessNamespaces provides the functionality requested in issue #30.