Skip to content

CHANGELOG.md

Latest commit

 

History

History
33 lines (21 loc) · 2.35 KB

CHANGELOG.md

File metadata and controls

33 lines (21 loc) · 2.35 KB

Change Log

[0.8] – 2015-06-27

  • The public API now has nullability annotations.
  • The public API now uses generics where available.
  • Some default values have changed when initializing nodes via init, in order to conform to the (now explicit) nullability annotations:
    • HTMLComment defaults to a data of "" (the empty string). Previously its default data was nil.
    • HTMLDocumentType defaults to a name of "html". Previously its default name was nil.
    • HTMLElement defaults to a tagName of "" (the empty string). Previously its default tagName was nil.
  • Nullability annotations for parameters are checked using NSParameterAssert. Some methods which previously returned nil when passed a nil parameter will now raise an assertion error. If you get assertion errors after upgrading where you previously did not get assertion errors, this may be why.
  • HTMLNode's -nodesMatchingSelector:, -firstNodeMatchingSelector, -nodesMatchingParsedSelector:, and -firstNodeMatchingParsedSelector: methods now always throw an NSInvalidArgumentException if the selector fails to parse. Previously they would raise an assertion, but otherwise fail in other (more poorly-defined) ways.
  • Use angle bracket imports (#import <HTMLReader/…>) throughout public headers, like a proper framework.

[0.7.1] – 2015-04-03

  • Selectors can now include escaped characters, allowing for e.g. matching elements like <some-ns:some-tag> using a selector like some-ns\:some-tag. Supported escapes are \XXXXXX for 1-6 hex digits X, and \c for any other character c.

[0.7] – 2015-03-16

  • Rename namespace properties to htmlNamespace to support compilation as Objective-C++.

[0.6.2] – 2015-03-15

  • Update build settings to allow HTMLReader.framework use in Swift on OS X.

[0.6.1] – 2015-02-06

  • Remove private header HTMLTextNode.h from the built framework.

[0.6] – 2015-02-06

  • A new document initializer, -[HTMLDocument initWithData:contentTypeHeader:], detects the character encoding as a browser would. This is the ideal initializer for HTML documents fetched over the network, or any other time when the character encoding isn't previously known. Note that HTML does not blindly use the encoding specified by the HTTP Content-Type header, so this initializer is still superior to parsing the Content-Type yourself.