Nested_params now recursively creates a nested indifferent hash from the already nested hash provided by Rack 1.0
* Check Content-Length against the GET response Content-Length to ensure that they stay in sync against future updates to the way Rack constructs its request headers hash. NOTE: HEAD response Content-Length seems to be off by 1 from equivalent GET response Content-Length. This matches the current (0.9.1.1) behavior but may no be intended.
Tiny yet potentially useful abstraction, allowing developers to tap into a route proc before it has been executed.
The previous behavior was to run only the main test suite, which led to missed compat issues. You can get the old behavior by running "rake test" explicitly.
* The options hash now takes the :views, :layout, and :locals options but also any template-specific options. The generic options are removed before calling the template specific render method. * The haml ":options" and ":haml" options are deprecated. These should be merged in directly with the options hash. * The sass ":sass" option is deprecated. Merge directly with the options hash instead. * All template engines have an app-level option named the same as their engine (erb, haml, sass, etc.). This must be a hash and is merged with the options passed to the render method. * The :views_directory option is deprecated; renamed :views.
Ensures globally set Haml/Sass configurations can be overridden on an individual call basis, while retaining the global values. Renamed the #haml() :options key to :haml_options for clarity and consistency with the #sass method.
…commit) * Retab * Use HTML5 and escape context_line so that it validates * Add space around backtrace "toggler" * Don't use blue for the "JUMP TO" link * Kill some newlines
The README is very ambiguous about the difference between passing a symbol and a string to a template rendering method. This adds a note that explains the difference.
While here, clean up some random cruft in the Rakefile