metainspector 4.7.0 → 4.7.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 329fa61a1fb5c278adb8c07c58536cc84e774f31
-  data.tar.gz: 8c40e805a960cc5591bee0317307dad27fa46719
+  metadata.gz: 76c49fb7187563a3e9daff74a8f3416521251fa6
+  data.tar.gz: 0c67668db7ec465badcbb6666b4d3183b1f3e70e
 SHA512:
-  metadata.gz: 0535544d927c37e963b567404764ff7af352c00afbfb896c44604e85d6e844155575d26b24a2234f478015f6f4aff9b75724d933c6cac9c3cceda6180545aa99
-  data.tar.gz: 9f7fa08ed92dcf775df62d97ab3a9d989c04ad4ff9ffe0cbaf6f83baf3c5bd052072d61e2db6b66ebef2643ca5de9de79e6aa78575a87bf432a21a3cb676a093
+  metadata.gz: 164db60a1bf7139c1fa4f92ad459073df0b0f0b2adf6a1c48aba960afcbcdcd02c8cbc66d4283b3b1f4967d8a1915f9aca2cf303384507ff74571cfaf17bf0c7
+  data.tar.gz: 3326aa3962c7136033557c4398c38a2f442e04d39d14656f7e8195a4b7de16e4f5f5e914a2a48d054ca808b7eff748543b1535f607a096a0a84c7819110c5b28

data/CHANGELOG.md

@@ -1,5 +1,19 @@
 # MetaInpector Changelog
 
+## [Changes in 4.7](https://github.com/jaimeiniesta/metainspector/compare/v4.6.0...v4.7.1)
+
+MetaInspector can be configured to use [Faraday::HttpCache](https://github.com/plataformatec/faraday-http-cache) to cache page responses. For that you should pass the `faraday_http_cache` option with at least the `:store` key, for example:
+
+```ruby
+cache = ActiveSupport::Cache.lookup_store(:file_store, '/tmp/cache')
+page = MetaInspector.new('http://example.com', faraday_http_cache: { store: cache })
+```
+
+Bugfixes:
+
+* Parsing of the document is done as soon as it is initialized (just like we do with the request), so
+that parsing errors will be catched earlier.
+
 ## [Changes in 4.6](https://github.com/jaimeiniesta/metainspector/compare/v4.5.0...v4.6.0)
 
 Faraday can be passed options via `:faraday_options`. This is useful in cases where we need to

data/README.md

@@ -393,6 +393,21 @@ You can also set the `warn_level: :store` option so that exceptions found will b
 
 You should avoid using the `:store` option, or use it wisely, as silencing errors can be problematic, it's always better to face the errors and treat them accordingly.
 
+If you're using this exception store, you're advised to first initialize the document, check if it seems OK, and then proceed with the extractions, like this:
+
+```ruby
+# This will fail because the URL will return a text/xml document
+page = MetaInspector.new("http://example.com/rss",
+                          html_content_only: true,
+                          warn_level: :store )
+
+if page.ok?
+  puts "TITLE: #{page.title}"
+else
+  puts "There were some exceptions: #{page.exceptions}"
+end
+```
+
 ## Examples
 
 You can find some sample scripts on the `examples` folder, including a basic scraping and a spider that will follow external links using a queue. What follows is an example of use from irb:

data/lib/meta_inspector/parser.rb

@@ -19,6 +19,8 @@ module MetaInspector
       @download_images = options[:download_images]
       @images_parser   = MetaInspector::Parsers::ImagesParser.new(self, download_images: @download_images)
       @texts_parser    = MetaInspector::Parsers::TextsParser.new(self)
+
+      parsed           # parse early so we can fail early
     end
 
     extend Forwardable

data/lib/meta_inspector/version.rb

@@ -1,3 +1,3 @@
 module MetaInspector
-  VERSION = '4.7.0'
+  VERSION = '4.7.1'
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: metainspector
 version: !ruby/object:Gem::Version
-  version: 4.7.0
+  version: 4.7.1
 platform: ruby
 authors:
 - Jaime Iniesta
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2015-10-21 00:00:00.000000000 Z
+date: 2015-10-22 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: nokogiri