# This file documents the revision history for Perl extension Catalyst.
-TBA
+5.90097 - 2015-07-28
- $c->uri_for now defines a final argument for setting the URL fragment
/URL anchor. This is now the canonical approach to setting a fragment
via uri_for.
+ - Reverted how we treat $c->uri_for($path) where $path is a string. When
+ we introduced the UTF-8 work we started encoding stringy paths, which
+ breaks code that did not expect that. We now consider stringy $path to
+ be 'expert' mode and you are expected to perform all nessary encoding.
5.90096 - 2015-07-27
- Fixed regression introduced in previous release that prevented a URI
__PACKAGE__->_encode_check(Encode::FB_CROAK | Encode::LEAVE_SRC);
# Remember to update this in Catalyst::Runtime as well!
-our $VERSION = '5.90096';
+our $VERSION = '5.90097';
$VERSION = eval $VERSION if $VERSION =~ /_/; # numify for warning-free dev releases
sub import {
# Remember to update this in Catalyst as well!
-our $VERSION = '5.90096';
+our $VERSION = '5.90097';
$VERSION = eval $VERSION if $VERSION =~ /_/; # numify for warning-free dev releases
=head1 NAME
https://localhost/foo/bar#fragment) by using a '#' in the path or final argument, for
example:
- $c->uri_for('/mypath#fragment');
-
-or:
-
$c->uri_for($action, 'foo#fragment');
This behavior was never documented and would break if using the Unicode plugin, or when
to match the new specification or modify uri_for for your local case. Patches to solve
this are very welcomed, as long as they don't break existing test cases.
-B<NOTE> If you are using the alternative:
+B<NOTE> If you are using the string form of the first argument:
$c->uri_for('/foo/bar#baz')