IssueRaiser

I was surprised there's no way to query the page beyond the small list of element accessors you provide (body, url, scheme, host, port, t...

I was surprised there's no way to query the page beyond the small list of element accessors you provide (body, url, scheme, host, port, title, description, links, images, meta). When you're putting together a tool like this, it's nice to give the user some way to "escape" your framework and get to lower level underlying data. Why not offer something like page.selector('h2 p') #returns Nokogiri elements page.h1 #calls method_missing, returns Nokogiri elements page.p #ditto page.noko #returns underlying Nokogiri doc Also, you forgot to include the body accessor in the "Accessing inpsected data" portion of the doc.

Posted by mapgrep on Jun 2, 2015, 2:24 PM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.6,000 issues0 comments

hackernews (Other)

I was surprised there's no way to query the page beyond the small list of element accessors you provide (body, url, scheme, host, port, t...

mapgrepJun 2, 2015, 2:24 PM

I was surprised there's no way to query the page beyond the small list of element accessors you provide (body, url, scheme, host, port, title, description, links, images, meta). When you're putting together a tool like this, it's nice to give the user some way to "escape" your framework and get to lower level underlying data. Why not offer something like page.selector('h2 p') #returns Nokogiri elements page.h1 #calls method_missing, returns Nokogiri elements page.p #ditto page.noko #returns underlying Nokogiri doc Also, you forgot to include the body accessor in the "Accessing inpsected data" portion of the doc.

Comments (0)

No comments yet. Start the discussion.

Comment on this issue