Permalink
Find file
63fb7b5 Feb 17, 2016
@flavorjones @leejarvis
112 lines (68 sloc) 3.55 KB

Roadmap for API Changes

overhaul serialize/pretty printing API

overhaul and optimize the SAX parsing

  • see fairy wing throwdown - SAX parsing is wicked slow.

Node should not be Enumerable; and should have a better attributes API

improve CSS query parsing

DocumentFragment

Better Syntax for custom XPath function handler

Better Syntax around Node#xpath and NodeSet#xpath

Encoding

We have a lot of issues open around encoding. How bad are things? Somebody who knows encoding well should head this up.

Reader

It's fundamentally broken, in that we can't stop people from crashing their application if they want to use object reference unsafely.

Class methods that require Document

There are a few methods, like Nokogiri::XML::Comment.new that require a Document object.

We should probably make Document instance methods to wrap this, since it's a non-obvious expectation and thus fails as a convention.

So, instead, let's make alternative methods like Nokogiri::XML::Document#new_comment, and recommend those as the proper convention.

collect_namespaces is just broken

collect_namespaces is returning a hash, which means it can't return namespaces with the same prefix. See this issue for background:

https://github.com/sparklemotion/nokogiri/issues/885

Do we care? This seems like a useless method, but then again I hate XML, so what do I know?