X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=catagits%2FCatalyst-Runtime.git;a=blobdiff_plain;f=Changes;h=79390595daced742323c290d87bf7d1d92b14470;hp=ae54fce517e6334410a9cc86f79e48dda1da3519;hb=9b7d26c74ea27e325f462a1f0e629a23809a4b8d;hpb=d71da6fe568d10f14edeeb8c4bb7280c577542d8

diff --git a/Changes b/Changes
index ae54fce..7939059 100644
--- a/Changes
+++ b/Changes
@@ -11,9 +11,28 @@
     - Catalyst::Test::local_request sets ->request on the response.
     - Require HTTP::Request 5.814 and HTTP::Response 5.813 from LWP 5.814
       to avoid test fails.
+    - Log flush moved to the end of setup so that roles and plugins which
+      hook setup_finalize can log things and have them appear in application
+      startup, rather than with the first hit.
+    - Require a newer version of LWP to avoid failing tests.
+    - Stop warnings when actions are forwarded to during dispatch.
+    - Remove warnings for using Catalyst::Dispatcher->dispatch_types as this is a
+      valid method to publicly call on the dispatcher.
+    - Args ($c->request->args) and CaptureArgs ($c->request->captrues)
+      passed to $c->uri_for with an action object ($c->action) will now
+      correctly round-trip when args or captures contain / as it is now
+      correctly uri encoded to %2F.
 
   Documentation:
     - Document no-args call to $c->uri_for.
+    - Document all top level application configuration parameters.
+    - Clarify how to fix actions in your application class (which is
+      deprecated and causes warnings).
+    - Pod fixes for ContextClosure.
+    - Fix documentation for go/visit to reference captures and arguments
+      in the correct order.
+    - Update $c->forward and $c->state documentation to address scalar
+      context.
 
   New features:
     - Added disable_component_resolution_regex_fallback config option to
@@ -23,6 +42,15 @@
     - Enable Catalyst::Utils::home() to find home within Dist::Zilla built
       distributions
 
+  Refactoring / cleanups:
+    - Remove documentation for the case_sensitive setting
+    - Warning is now emitted at application startup if the case_sensitive
+      setting is turned on. This setting is not used by anyone, not
+      believed to be useful and adds unnecessary complexity to controllers
+      and the dispatcher. If you are using this setting and have good reasons
+      why it should stay then you need to be shouting, now.
+    - Writing to $c->req->body now fails as doing this never makes sense.
+
 5.80013 2009-09-17 11:07:04
 
    Bug fixes: