v1.40

- Added diagnostic for IO loop implementation in testing

Changes

@@ -1,6 +1,14 @@
 Revision history for Mojolicious::Plugin::TtRenderer
 
 {{$NEXT}}
+
+1.40    February 20, 2013
+        - Added diagnostic for IO loop implementation in testing
+
+1.39    January 28, 2013
+        - Documentation updates.
+
+1.38    January 27, 2013
         - fixed but where DATA templates were not being rendered with empty renderer path
 
 1.37    January 12, 2013

README.pod

@@ -38,7 +38,10 @@ The current controller instance can be accessed as C<c>.
 
 =head1 SEE ALSO
 
-L<Mojolicious::Plugin::TtRenderer::Engine>, L<Mojolicious>, L<Mojolicious::Guides>, L<http://mojolicious.org>.
+L<Mojolicious::Plugin::TtRenderer::Engine>, 
+L<Mojolicious>, 
+L<Mojolicious::Guides>, 
+L<http://mojolicious.org>.
 
 =head1 AUTHOR
 

dist.ini

@@ -12,6 +12,9 @@ Template     = 2.18
 [Prereqs / TestRequires ]
 Test::More   = 0
 
+[NextRelease]
+format = %-7v %{MMMM d, yyyy}d
+
 [@Git]
 tag_format = release/%v
 # push_to    = all
@@ -51,9 +54,6 @@ location = root
 
 [Manifest]
 
-[NextRelease]
-format = %-7v %{MMMM d, yyyy}d
-
 [MinimumPerl]
 
 [MetaJSON]

lib/Mojolicious/Plugin/TtRenderer.pm

@@ -64,7 +64,10 @@ The current controller instance can be accessed as C<c>.
 
 =head1 SEE ALSO
 
-L<Mojolicious::Plugin::TtRenderer::Engine>, L<Mojolicious>, L<Mojolicious::Guides>, L<http://mojolicious.org>.
+L<Mojolicious::Plugin::TtRenderer::Engine>, 
+L<Mojolicious>, 
+L<Mojolicious::Guides>, 
+L<http://mojolicious.org>.
 
 =head1 AUTHOR
 

lib/Mojolicious/Plugin/TtRenderer/Engine.pm

@@ -42,12 +42,10 @@ sub _init {
     #   take and process options :-)
 
     my @renderer_paths = $app ? map { abs_path($_) } grep { -d $_ } @{ $app->renderer->paths } : ();
+    push @renderer_paths, 'templates';
 
     my %config = (
-        (   @renderer_paths > 0
+        INCLUDE_PATH => \@renderer_paths,
-            ? (INCLUDE_PATH => [@renderer_paths, 'templates'])
-            : (INCLUDE_PATH => ['templates'])
-        ),
         COMPILE_EXT  => '.ttc',
         COMPILE_DIR  => ($dir || abs_path(File::Spec->tmpdir)),
         UNICODE      => 1,
@@ -288,7 +286,11 @@ object. When used the INCLUDE_PATH will be set to
 
 =item template_options
 
-A hash reference of options that are passed to Template->new().
+A hash reference of options that are passed to Template->new().  Note that if you
+specify an C<INCLUDE_PATH> through this option it will remove the DATA section
+templates from your path.  A better way to specify an C<INCLUDE_PATH> if you also
+want to use DATA section templates it by manipulting the L<Mojolicious::Renderer>
+path.
 
 =item cache_dir
 
@@ -297,18 +299,19 @@ templates. Will default to a temp-dir if not set.
 
 =back
 
+=head1 SEE ALSO
+
+L<Mojolicious::Plugin::TtRenderer::Engine>, 
+L<Mojolicious>, 
+L<Mojolicious::Guides>, 
+L<http://mojolicious.org>.
+
 =head1 AUTHOR
 
 Current maintainer: Graham Ollis C<< <plicease@cpan.org> >>
 
 Original author: Ask Bjørn Hansen, C<< <ask at develooper.com> >>
 
-=head1 TODO
-
-   * Better support non-Mojolicious frameworks
-   * Better way to pass parameters to the templates? (stash)
-   * More sophisticated default search path?
-
 =head1 BUGS
 
 Please report any bugs or feature requests to the project's github issue tracker

t/01-ioloop.t

@@ -0,0 +1,11 @@
+use strict;
+use warnings;
+use Test::More tests => 1;
+use Mojo::IOLoop;
+
+my $loop = eval { Mojo::IOLoop->singleton };
+diag $@ if $@;
+ok $loop;
+diag ref eval { $loop->reactor };
+diag $@ if $@;
+