[Dancer-users] template() behaviour change in 1.3090 (immediately returning)

[sawyer x]

A new release (1.3091) is out on CPAN!
It's got a few changes, most notably the return of the old template() call.
Here is the changelog entry:
1.3091      17.12.2011

    [ BUG FIXES ]
    * Reverting template() behavior by popular demand. (Damien Krotkine)
    * GH #714: Run post-request hooks when custom continuations were
created.
      (Damien Krotkine)
    * Always call write_session_id() to update expires. (David Precious)

    [ ENHANCEMENTS ]
    * GH #711, #652: Add server_tokens variable to allow removal of headers.
      (John Wittkoski)

    [ DOCUMENTATION ]
    * GH #680: Document problems with multiple apps in Dancer using
      Plack::Handler::Apache2 and recommend a workaround.
      (Asaf Gordon, Pedro Melo)
    * RT #73258: Spelling glitches. (Damyan Ivanov)
    * Use ":script" instead of ":syntax" in Cookbook. (John Barrett)
    * Typos in Deployment doc. (David Precious)

All in all, 5 tickets were resolved. Good job everyone!

On Sat, Dec 17, 2011 at 11:26 AM, sawyer x <xsawyerx at gmail.com> wrote:

> Whoops!
>
> I responded in the wrong thread... :)
>
>
>
> On Fri, Dec 16, 2011 at 2:56 PM, damien krotkine <dkrotkine at gmail.com>wrote:
>
>> Well your code will stil work, no need to change anything
>>
>>
>> On 16 December 2011 13:33, Nick Knutov <mail at knutov.com> wrote:
>> > I always do something like
>> >
>> > return redirect '/error/?reason=...' unless pass_all_checks()
>> >
>> > I think I read in documentation or examples that it should be so and
>> this
>> > way looks better - I can decide how it will work.
>> >
>> > I think it's better to make accent on using 'return' when it needed, not
>> > changing behavior.
>> >
>> > 16.12.2011 18:16, damien krotkine пишет:
>> >
>> >> On 16 December 2011 12:57, Nick Knutov<mail at knutov.com>  wrote:
>> >>>
>> >>> +1.
>> >>>
>> >>> As pass() and other.
>> >>>
>> >>> Btw, are any reasons at all to halt the execution of the route
>> handler in
>> >>> this functions?
>> >>
>> >>
>> >> There were a nasty security issue that if you uses a hook to catch the
>> >> fact that a user is not authenticated for instance, the workflow would
>> >> still continue in the rest of the route, so we needed a way to stop
>> >> the execution of the route code block only.
>> >
>> >
>> > --
>> > Best Regards,
>> > Nick Knutov
>> > http://knutov.com
>> > ICQ: 272873706
>> > Voice: +7-904-84-23-130
>> _______________________________________________
>> Dancer-users mailing list
>> Dancer-users at perldancer.org
>> http://www.backup-manager.org/cgi-bin/listinfo/dancer-users
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.backup-manager.org/pipermail/dancer-users/attachments/20111217/37aab103/attachment.htm>