view_inspect 0.3.7 → 0.3.8

checksums.yaml

@@ -1,15 +1,15 @@
 ---
 !binary "U0hBMQ==":
   metadata.gz: !binary |-
-    OTY0NTA1MTUwYTE4ZTAzNDY0ODA2MmVmNWQ3Nzk1OTlkNzY0ZjI3NQ==
+    NDRmZTg4YmJjMGQ4ZTdkM2Q4ZjYxNjcxZWVjNDg1MzI4Yzc2YjRiNQ==
   data.tar.gz: !binary |-
-    YTRhY2FlY2I5OTZkMzc1NGM5ODI1ZmUwZTFmZGE1ZGRjMDQ1MTA1YQ==
+    YmE4MTlmMDc1MWYwY2Q2OTE0YmIxMjgzODIxODI0NGI1YTNhZDIxMw==
 SHA512:
   metadata.gz: !binary |-
-    YmVhYjMyYjgxMGYxMTI2ZmE0ZWZiMWY2Njg4MDA0ZTUyYzU3Y2FhNmM5MWZl
-    MDdlOTZlMDEyYmNlZWViZjM3Zjc1ZWUwZjQwYTZkMjFlN2EwYWE4Nzg1NDEy
-    ZTlkMzUxYWQ4ZGNmOWVhYTA2ZTgyY2IxY2UyNGQ3Zjk5MzhkZDM=
+    ZTI5OWZlZDM5ODY2NzlkMzQwYWQ2NzVlMDBjNjE5MzRiZjRjYTk2ZDdlMGVm
+    MWIzOGM3MGYzNzE0NjUxZjkyYzc5MTYzZWYwYWVmMTQxYWZkZjQyN2ExMjJm
+    ZmZlMDVlNTA1ZDM4YWM1ZTRkZjE4ZjYzNWI3MWRiNDFjNGQyMmM=
   data.tar.gz: !binary |-
-    ZjY2YjBhNjdlY2IzZWQ3MGRkNGViN2YxOTZhNjRhMWIyNzQ5MGIwZjNjY2Y5
-    Y2Y2ZDJkZjkyNjk5MDcyYzc5YzllMDM5ZjE4MWM1ZTA5ODgwYWYxNWRjMjg2
-    ZDc5ZWVkZWEyZGEyYzhkYzg2NjIxNGE5MDJmMTgxZmM4NTVhMjU=
+    ZmZhYzJmZDkyZWU2NjlhZGIwNDg3YjUzZTk4ZDFmNjI3MmEwNDllNTNmZjk1
+    MTBhMTMzN2ZmY2NmNzZhYmI4ZWI5ZGRiNWZlNmI0MTEyNjIyMTUzYWRlOTE5
+    MDZiMmEzNDFmYTM0Y2Q1NmY0MzJlNTQxNjA0M2RlODk5NmNhNGM=

data/README.markdown

@@ -1,7 +1,7 @@
 View Inspect
 ============
 
-View Inspect tells you which server-side or client-side template is responsible for rendering a DOM element. Instead of using grep to filter through a large codebase, the source location can be found right away in its data-attribute when you open up web inspector. Works with Rails 3 and 4. See below for templates supported and their required libraries.
+View Inspect shows you the exact file and line number of the server-side or client-side template that's responsible for rendering a DOM element. Instead of using grep to filter through a large codebase, the source location can be found right away in its data-attribute when you open up web inspector. Works with Rails 3 and 4. See below for templates supported and their required libraries.
 
 Demo
 ----
@@ -38,7 +38,7 @@ By default, this is only enabled for development to avoid exposing source code f
 How it Works
 ----
 
-Except for Haml and Slim where the compiler/parser is monkeypatched to include file:line information to each node, the rest of the templates are augment by preprocessing them with an HTML parser. Basically, we first stub out all template specific expressions (i.e. `<% %>` for erb) from a template file. Then, we use the Nokogiri HTML Parser to parse the resulting valid HTML fragment, and add file:line information to its child nodes. Once this is done, we bring back our original template expressions and remove the stubs. A little bit hacky but it works.
+Except for Haml and Slim where the compiler/parser is monkeypatched, view templates are augmented with source location metadata by preprocessing them with an HTML parser. Basically, we first stub out all template specific expressions (i.e. `<% %>` for erb) from a template file. Then, we use the Nokogiri HTML Parser to parse the resulting valid HTML fragment, and add file:line information to its child nodes. Once this is done, we bring back our original template expressions and remove the stubs. A little bit hacky but it works.
 
 
 Server-Side Templates
@@ -55,11 +55,13 @@ For client-side templates to work, they have to live in separate files as oppose
 
 HTML Syntax Errors
 ----
-ViewInspect depends on Nokogiri to preprocess a template and add file:line information to each node. If there's any invalid HTML in your file, Nokogiri would delete it, and sometimes your HTML would look different in the browser because of this. To prevent that from happening, a Warning message would be shown to the user detailing where the HTML syntax errors are located so that the user can remove it. This is the default behavior.
+ViewInspect depends on Nokogiri to preprocess a template and add file:line information to each node. If there's any invalid HTML in your file, Nokogiri would delete it, and sometimes your HTML would look different in the browser because of this.
 
-An alternative solution is to avoid adding file:line information to DOM elements whenever Nokogiri encounters HTML syntax errors. Instead, it'll just show the original HTML template. If you prefer this behavior, you can set it by adding this line to config/environments/development.rb
+If such errors exist, view_inspect would simply return the original file template without the source location metadata to avoid malformed html.
 
-    ViewInspect.show_html_syntax_error = false
+An alternative solution is to show a warning message to the user detailing where the HTML syntax errors are located so that the user can remove it. To enable this, you can set it by adding this line to config/environments/development.rb
+
+    ViewInspect.show_html_syntax_error = true
 
 Copyright
 ----

data/lib/view_inspect/version.rb

@@ -1,3 +1,3 @@
 module ViewInspect
-  VERSION = "0.3.7"
+  VERSION = "0.3.8"
 end

data/lib/view_inspect.rb

@@ -9,7 +9,7 @@ module ViewInspect
     ServerSideTemplate.handle
     ClientSideTemplate.handle
 
-    @show_html_syntax_error = true
+    @show_html_syntax_error = false
   end
 
   def self.allow_view_source_location?

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: view_inspect
 version: !ruby/object:Gem::Version
-  version: 0.3.7
+  version: 0.3.8
 platform: ruby
 authors:
 - Reginald Tan
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2014-11-15 00:00:00.000000000 Z
+date: 2014-11-22 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: nokogiri