uri_for and prefix don't seem to work as expected

[estrella-red]

Hello, I have recently returned to Dancer2 (1.1.2) after a long absence, an am struggling to make sense of uri_for and uri_for_route when used under prefix. uri_for works fine when my app uses a single routes file, but as soon as I split into 2 (or more), as shown in cookbook, uri_for ignores the prefix so my url's don't work. So:

prefix undef;
get '/edit' => sub { say request->uri_for('/search') }; # '/search'
prefix '/info';
get '/update' => sub { say request->uri_for('/delete') }; # /delete - should be '/info/delete'

the same behaviour in templates: request.uri_for('/search')) omits the prefix when it should exist

uri_for_route does recognise the prefix, but fails if the route contains a 'forward', generating an error "uri_for_route called on a request instance without it" at line #323 in D2::Core::Request due to $self->{'uri_for_route'} being undef. Incidentally this error message is rather unhelpful.

Something I am doing wrong, or bugs?

[estrella-red]

I know what is happening to cause uri_for_route to fail on forward:

get '/foo' => sub { print Dumper request; 1 }
get '/bar' => sub { print Dumper request; forward '/foo' };

http request for /bar prior to forward:

[...]
uri_for_route => sub {
      package Dancer2::Core::App;
      use warnings;
      use strict;
      shift();
      $weak_self->uri_for_route(@_);
  },

http request for /bar after forward to /foo:
uri_for_route => undef

This behaviour is alluded to in the docs "when forward is executed, the current dispatch of the route is aborted, the request is modified". Can this be changed so that uri_for_route is preserved?