actionpack 4.0.13 → 4.1.0.beta1

data/lib/action_view/helpers/cache_helper.rb

@@ -1,196 +0,0 @@
-module ActionView
-  # = Action View Cache Helper
-  module Helpers
-    module CacheHelper
-      # This helper exposes a method for caching fragments of a view
-      # rather than an entire action or page. This technique is useful
-      # caching pieces like menus, lists of newstopics, static HTML
-      # fragments, and so on. This method takes a block that contains
-      # the content you wish to cache.
-      #
-      # The best way to use this is by doing key-based cache expiration
-      # on top of a cache store like Memcached that'll automatically
-      # kick out old entries. For more on key-based expiration, see:
-      # http://37signals.com/svn/posts/3113-how-key-based-cache-expiration-works
-      #
-      # When using this method, you list the cache dependency as the name of the cache, like so:
-      #
-      #   <% cache project do %>
-      #     <b>All the topics on this project</b>
-      #     <%= render project.topics %>
-      #   <% end %>
-      #
-      # This approach will assume that when a new topic is added, you'll touch
-      # the project. The cache key generated from this call will be something like:
-      #
-      #   views/projects/123-20120806214154/7a1156131a6928cb0026877f8b749ac9
-      #         ^class   ^id ^updated_at    ^template tree digest
-      #
-      # The cache is thus automatically bumped whenever the project updated_at is touched.
-      #
-      # If your template cache depends on multiple sources (try to avoid this to keep things simple),
-      # you can name all these dependencies as part of an array:
-      #
-      #   <% cache [ project, current_user ] do %>
-      #     <b>All the topics on this project</b>
-      #     <%= render project.topics %>
-      #   <% end %>
-      #
-      # This will include both records as part of the cache key and updating either of them will
-      # expire the cache.
-      #
-      # ==== Template digest
-      #
-      # The template digest that's added to the cache key is computed by taking an md5 of the
-      # contents of the entire template file. This ensures that your caches will automatically
-      # expire when you change the template file.
-      #
-      # Note that the md5 is taken of the entire template file, not just what's within the
-      # cache do/end call. So it's possible that changing something outside of that call will
-      # still expire the cache.
-      #
-      # Additionally, the digestor will automatically look through your template file for
-      # explicit and implicit dependencies, and include those as part of the digest.
-      #
-      # The digestor can be bypassed by passing skip_digest: true as an option to the cache call:
-      #
-      #   <% cache project, skip_digest: true do %>
-      #     <b>All the topics on this project</b>
-      #     <%= render project.topics %>
-      #   <% end %>
-      #
-      # ==== Implicit dependencies
-      #
-      # Most template dependencies can be derived from calls to render in the template itself.
-      # Here are some examples of render calls that Cache Digests knows how to decode:
-      #
-      #   render partial: "comments/comment", collection: commentable.comments
-      #   render "comments/comments"
-      #   render 'comments/comments'
-      #   render('comments/comments')
-      #
-      #   render "header" => render("comments/header")
-      #
-      #   render(@topic)         => render("topics/topic")
-      #   render(topics)         => render("topics/topic")
-      #   render(message.topics) => render("topics/topic")
-      #
-      # It's not possible to derive all render calls like that, though. Here are a few examples of things that can't be derived:
-      #
-      #   render group_of_attachments
-      #   render @project.documents.where(published: true).order('created_at')
-      #
-      # You will have to rewrite those to the explicit form:
-      #
-      #   render partial: 'attachments/attachment', collection: group_of_attachments
-      #   render partial: 'documents/document', collection: @project.documents.where(published: true).order('created_at')
-      #
-      # === Explicit dependencies
-      #
-      # Some times you'll have template dependencies that can't be derived at all. This is typically
-      # the case when you have template rendering that happens in helpers. Here's an example:
-      #
-      #   <%= render_sortable_todolists @project.todolists %>
-      #
-      # You'll need to use a special comment format to call those out:
-      #
-      #   <%# Template Dependency: todolists/todolist %>
-      #   <%= render_sortable_todolists @project.todolists %>
-      #
-      # The pattern used to match these is /# Template Dependency: ([^ ]+)/, so it's important that you type it out just so.
-      # You can only declare one template dependency per line.
-      #
-      # === External dependencies
-      #
-      # If you use a helper method, for example, inside of a cached block and you then update that helper,
-      # you'll have to bump the cache as well. It doesn't really matter how you do it, but the md5 of the template file
-      # must change. One recommendation is to simply be explicit in a comment, like:
-      #
-      #   <%# Helper Dependency Updated: May 6, 2012 at 6pm %>
-      #   <%= some_helper_method(person) %>
-      #
-      # Now all you'll have to do is change that timestamp when the helper method changes.
-      def cache(name = {}, options = nil, &block)
-        if controller.perform_caching
-          safe_concat(fragment_for(cache_fragment_name(name, options), options, &block))
-        else
-          yield
-        end
-
-        nil
-      end
-
-      # Cache fragments of a view if +condition+ is true
-      #
-      #   <%= cache_if admin?, project do %>
-      #     <b>All the topics on this project</b>
-      #     <%= render project.topics %>
-      #   <% end %>
-      def cache_if(condition, name = {}, options = nil, &block)
-        if condition
-          cache(name, options, &block)
-        else
-          yield
-        end
-
-        nil
-      end
-
-      # Cache fragments of a view unless +condition+ is true
-      #
-      #   <%= cache_unless admin?, project do %>
-      #     <b>All the topics on this project</b>
-      #     <%= render project.topics %>
-      #   <% end %>
-      def cache_unless(condition, name = {}, options = nil, &block)
-        cache_if !condition, name, options, &block
-      end
-
-      # This helper returns the name of a cache key for a given fragment cache
-      # call. By supplying skip_digest: true to cache, the digestion of cache
-      # fragments can be manually bypassed. This is useful when cache fragments
-      # cannot be manually expired unless you know the exact key which is the
-      # case when using memcached.
-      def cache_fragment_name(name = {}, options = nil)
-        skip_digest = options && options[:skip_digest]
-
-        if skip_digest
-          name
-        else
-          fragment_name_with_digest(name)
-        end
-      end
-
-    private
-
-      def fragment_name_with_digest(name) #:nodoc:
-        if @virtual_path
-          [
-            *Array(name.is_a?(Hash) ? controller.url_for(name).split("://").last : name),
-            Digestor.digest(@virtual_path, formats.last.to_sym, lookup_context, dependencies: view_cache_dependencies)
-          ]
-        else
-          name
-        end
-      end
-
-      # TODO: Create an object that has caching read/write on it
-      def fragment_for(name = {}, options = nil, &block) #:nodoc:
-        if fragment = controller.read_fragment(name, options)
-          fragment
-        else
-          # VIEW TODO: Make #capture usable outside of ERB
-          # This dance is needed because Builder can't use capture
-          pos = output_buffer.length
-          yield
-          output_safe = output_buffer.html_safe?
-          fragment = output_buffer.slice!(pos..-1)
-          if output_safe
-            self.output_buffer = output_buffer.class.new(output_buffer)
-          end
-          controller.write_fragment(name, fragment, options)
-        end
-      end
-    end
-  end
-end

data/lib/action_view/helpers/capture_helper.rb

@@ -1,216 +0,0 @@
-require 'active_support/core_ext/string/output_safety'
-
-module ActionView
-  # = Action View Capture Helper
-  module Helpers
-    # CaptureHelper exposes methods to let you extract generated markup which
-    # can be used in other parts of a template or layout file.
-    #
-    # It provides a method to capture blocks into variables through capture and
-    # a way to capture a block of markup for use in a layout through content_for.
-    module CaptureHelper
-      # The capture method allows you to extract part of a template into a
-      # variable. You can then use this variable anywhere in your templates or layout.
-      #
-      # The capture method can be used in ERB templates...
-      #
-      #   <% @greeting = capture do %>
-      #     Welcome to my shiny new web page!  The date and time is
-      #     <%= Time.now %>
-      #   <% end %>
-      #
-      # ...and Builder (RXML) templates.
-      #
-      #   @timestamp = capture do
-      #     "The current timestamp is #{Time.now}."
-      #   end
-      #
-      # You can then use that variable anywhere else. For example:
-      #
-      #   <html>
-      #   <head><title><%= @greeting %></title></head>
-      #   <body>
-      #   <b><%= @greeting %></b>
-      #   </body></html>
-      #
-      def capture(*args)
-        value = nil
-        buffer = with_output_buffer { value = yield(*args) }
-        if string = buffer.presence || value and string.is_a?(String)
-          ERB::Util.html_escape string
-        end
-      end
-
-      # Calling content_for stores a block of markup in an identifier for later use.
-      # In order to access this stored content in other templates, helper modules
-      # or the layout, you would pass the identifier as an argument to <tt>content_for</tt>.
-      #
-      # Note: <tt>yield</tt> can still be used to retrieve the stored content, but calling
-      # <tt>yield</tt> doesn't work in helper modules, while <tt>content_for</tt> does.
-      #
-      #   <% content_for :not_authorized do %>
-      #     alert('You are not authorized to do that!')
-      #   <% end %>
-      #
-      # You can then use <tt>content_for :not_authorized</tt> anywhere in your templates.
-      #
-      #   <%= content_for :not_authorized if current_user.nil? %>
-      #
-      # This is equivalent to:
-      #
-      #   <%= yield :not_authorized if current_user.nil? %>
-      #
-      # <tt>content_for</tt>, however, can also be used in helper modules.
-      #
-      #   module StorageHelper
-      #     def stored_content
-      #       content_for(:storage) || "Your storage is empty"
-      #     end
-      #   end
-      #
-      # This helper works just like normal helpers.
-      #
-      #   <%= stored_content %>
-      #
-      # You can also use the <tt>yield</tt> syntax alongside an existing call to
-      # <tt>yield</tt> in a layout. For example:
-      #
-      #   <%# This is the layout %>
-      #   <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
-      #   <head>
-      #     <title>My Website</title>
-      #     <%= yield :script %>
-      #   </head>
-      #   <body>
-      #     <%= yield %>
-      #   </body>
-      #   </html>
-      #
-      # And now, we'll create a view that has a <tt>content_for</tt> call that
-      # creates the <tt>script</tt> identifier.
-      #
-      #   <%# This is our view %>
-      #   Please login!
-      #
-      #   <% content_for :script do %>
-      #     <script>alert('You are not authorized to view this page!')</script>
-      #   <% end %>
-      #
-      # Then, in another view, you could to do something like this:
-      #
-      #   <%= link_to 'Logout', action: 'logout', remote: true %>
-      #
-      #   <% content_for :script do %>
-      #     <%= javascript_include_tag :defaults %>
-      #   <% end %>
-      #
-      # That will place +script+ tags for your default set of JavaScript files on the page;
-      # this technique is useful if you'll only be using these scripts in a few views.
-      #
-      # Note that content_for concatenates (default) the blocks it is given for a particular
-      # identifier in order. For example:
-      #
-      #   <% content_for :navigation do %>
-      #     <li><%= link_to 'Home', action: 'index' %></li>
-      #   <% end %>
-      #
-      #  And in other place:
-      #
-      #   <% content_for :navigation do %>
-      #     <li><%= link_to 'Login', action: 'login' %></li>
-      #   <% end %>
-      #
-      # Then, in another template or layout, this code would render both links in order:
-      #
-      #   <ul><%= content_for :navigation %></ul>
-      #
-      # If the flush parameter is true content_for replaces the blocks it is given. For example:
-      #
-      #   <% content_for :navigation do %>
-      #     <li><%= link_to 'Home', action: 'index' %></li>
-      #   <% end %>
-      #
-      #   <%#  Add some other content, or use a different template: %>
-      #
-      #   <% content_for :navigation, flush: true do %>
-      #     <li><%= link_to 'Login', action: 'login' %></li>
-      #   <% end %>
-      #
-      # Then, in another template or layout, this code would render only the last link:
-      #
-      #   <ul><%= content_for :navigation %></ul>
-      #
-      # Lastly, simple content can be passed as a parameter:
-      #
-      #   <% content_for :script, javascript_include_tag(:defaults) %>
-      #
-      # WARNING: content_for is ignored in caches. So you shouldn't use it for elements that will be fragment cached.
-      def content_for(name, content = nil, options = {}, &block)
-        if content || block_given?
-          if block_given?
-            options = content if content
-            content = capture(&block)
-          end
-          if content
-            options[:flush] ? @view_flow.set(name, content) : @view_flow.append(name, content)
-          end
-          nil
-        else
-          @view_flow.get(name).presence
-        end
-      end
-
-      # The same as +content_for+ but when used with streaming flushes
-      # straight back to the layout. In other words, if you want to
-      # concatenate several times to the same buffer when rendering a given
-      # template, you should use +content_for+, if not, use +provide+ to tell
-      # the layout to stop looking for more contents.
-      def provide(name, content = nil, &block)
-        content = capture(&block) if block_given?
-        result = @view_flow.append!(name, content) if content
-        result unless content
-      end
-
-      # content_for? checks whether any content has been captured yet using `content_for`.
-      # Useful to render parts of your layout differently based on what is in your views.
-      #
-      #   <%# This is the layout %>
-      #   <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
-      #   <head>
-      #     <title>My Website</title>
-      #     <%= yield :script %>
-      #   </head>
-      #   <body class="<%= content_for?(:right_col) ? 'two-column' : 'one-column' %>">
-      #     <%= yield %>
-      #     <%= yield :right_col %>
-      #   </body>
-      #   </html>
-      def content_for?(name)
-        @view_flow.get(name).present?
-      end
-
-      # Use an alternate output buffer for the duration of the block.
-      # Defaults to a new empty string.
-      def with_output_buffer(buf = nil) #:nodoc:
-        unless buf
-          buf = ActionView::OutputBuffer.new
-          buf.force_encoding(output_buffer.encoding) if output_buffer
-        end
-        self.output_buffer, old_buffer = buf, output_buffer
-        yield
-        output_buffer
-      ensure
-        self.output_buffer = old_buffer
-      end
-
-      # Add the output buffer to the response body and start a new one.
-      def flush_output_buffer #:nodoc:
-        if output_buffer && !output_buffer.empty?
-          response.stream.write output_buffer
-          self.output_buffer = output_buffer.respond_to?(:clone_empty) ? output_buffer.clone_empty : output_buffer[0, 0]
-          nil
-        end
-      end
-    end
-  end
-end

data/lib/action_view/helpers/controller_helper.rb

@@ -1,25 +0,0 @@
-require 'active_support/core_ext/module/attr_internal'
-
-module ActionView
-  module Helpers
-    # This module keeps all methods and behavior in ActionView
-    # that simply delegates to the controller.
-    module ControllerHelper #:nodoc:
-      attr_internal :controller, :request
-
-      delegate :request_forgery_protection_token, :params, :session, :cookies, :response, :headers,
-               :flash, :action_name, :controller_name, :controller_path, :to => :controller
-
-      def assign_controller(controller)
-        if @_controller = controller
-          @_request = controller.request if controller.respond_to?(:request)
-          @_config  = controller.config.inheritable_copy if controller.respond_to?(:config)
-        end
-      end
-
-      def logger
-        controller.logger if controller.respond_to?(:logger)
-      end
-    end
-  end
-end

data/lib/action_view/helpers/csrf_helper.rb

@@ -1,32 +0,0 @@
-module ActionView
-  # = Action View CSRF Helper
-  module Helpers
-    module CsrfHelper
-      # Returns meta tags "csrf-param" and "csrf-token" with the name of the cross-site
-      # request forgery protection parameter and token, respectively.
-      #
-      #   <head>
-      #     <%= csrf_meta_tags %>
-      #   </head>
-      #
-      # These are used to generate the dynamic forms that implement non-remote links with
-      # <tt>:method</tt>.
-      #
-      # You don't need to use these tags for regular forms as they generate their own hidden fields.
-      #
-      # For AJAX requests other than GETs, extract the "csrf-token" from the meta-tag and send as the
-      # "X-CSRF-Token" HTTP header. If you are using jQuery with jquery-rails this happens automatically.
-      def csrf_meta_tags
-        if protect_against_forgery?
-          [
-            tag('meta', :name => 'csrf-param', :content => request_forgery_protection_token),
-            tag('meta', :name => 'csrf-token', :content => form_authenticity_token)
-          ].join("\n").html_safe
-        end
-      end
-
-      # For backwards compatibility.
-      alias csrf_meta_tag csrf_meta_tags
-    end
-  end
-end