Giter VIP home page Giter VIP logo

catalyst-view-xslate's People

Contributors

garu avatar getty avatar gfx avatar hiratara avatar jjn1056 avatar lestrrat avatar sunnavy avatar wreis avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar

catalyst-view-xslate's Issues

Test suite creates temp files with fixed path

Hello,

Please see the following test failure:

`Output from './Build test':

t/003_helper.t ....... ok
t/001_load.t ......... ok

Failed test 'use Catalyst::Test;'

at t/005_memory_leak.t line 9.

Tried to use 'Catalyst::Test'.

Error: Couldn't instantiate component "TestApp::View::Xslate::SJIS", "mkdir /tmp/TestApp/%2Fhome%2Fcpan4%2F.cpan%2Fbuild%2FCatalyst-View-Xslate-0.00019-0%2Ft%2Flib%2FTestApp%2Froot/: Permission denied at /home/cpan4/install/lib/perl5/site_perl/5.25.6/Catalyst/Test.pm line 155.

BEGIN failed--compilation aborted at t/005_memory_leak.t line 9.

Undefined subroutine &main::ctx_request called at t/005_memory_leak.t line 13.

Looks like your test exited with 255 just after 1.

t/005_memory_leak.t ..
Dubious, test returned 255 (wstat 65280, 0xff00)
Failed 3/3 subtests

Failed test 'use Catalyst::Test;'

at t/002_render.t line 7.

Tried to use 'Catalyst::Test'.`

This occurs because your testsuite attempts to create a temporary directory with a hardcoded name (specifically, /tmp/TestApp). However, if another user has already built your module on the same computer, it will be impossible to access that directory. Please consider using a non-hardcoded name for your top-level temporary directory.

Tests fail with Catalyst 5.90111

See subject.

A sample fail report: http://www.cpantesters.org/cpan/report/2faa1176-5250-11e6-b6f4-8bdfed09dfea

Statistical analysis (negative theta is bad):

****************************************************************
Regression 'mod:Catalyst'
****************************************************************
Name                   Theta          StdErr     T-stat
[0='const']           1.0000          0.0000    111412901754845408.00
[1='eq_5.90097']              0.0000          0.0000       0.00
[2='eq_5.90100']              0.0000          0.0000       0.00
[3='eq_5.90101']              0.0000          0.0000       0.00
[4='eq_5.90102']              0.0000          0.0000       0.00
[5='eq_5.90103']              0.0000          0.0000       0.00
[6='eq_5.90104']              0.0000          0.0000       0.00
[7='eq_5.90105']              0.0000          0.0000       0.00
[8='eq_5.90106']              0.0000          0.0000       0.00
[9='eq_5.90111']             -1.0000          0.0000    -90968253354067904.00

R^2= 1.000, N= 61, K= 10
****************************************************************

No way to pass pre_process_handler to Xslate

Catalyst::View::Xslate doesn't have a pre_process_handler attribute, so there's no easy way to set one for Text::Xslate.

Maybe there should just be an additional_xslate_args hash. That way, you wouldn't need to update Catalyst::View::Xslate any time Text::Xslate got a new configuration option.

I've worked around this with an around handler on _build_xslate, but that's poking into the internals in a way I'd like to avoid.

suffix and template extension

follow up for RT #68799 and to resummarize here (sorry, just hating on RT)

suffix is not provided per docs in CVX::Helper in 0.12.

patch was added in the latest git.

The project I had been working on was killed / or moved to dancer; so I apologize for not getting back to you.

It looks like the test now passes if suffix is defined.

However, I I'm not sure I understand the difference between suffix and template_extension. It seems that the former is for Text::Xslate and the latter is for Catalyst. However, why would I want both? it would seem that perhaps they should simply be an alias? DWIM principle.

Managing cache

Is it available to manage a cache of templates in controller?
It will be pretty useful if it could be managed over stash('cache_template') for example.

Attributes that should clear xslate don't

The documentation says that attributes that are passed along to the Text::Xslate constructor cause any previously-constructed Text::Xslate object to be cleared. But you left off the trigger that does the clearing from some of the documented attributes.

In particular, I noticed line_start, tag_start, tag_end, warn_handler, die_handler, and pre_process_handler all have this problem. There might be others I missed.

Additional path for templates

I want to set up a path for templates files in controller. In TT it's available over $c->stash->{'additional_template_paths'} = [...];
Is it available in Catalyst::View::Xslate? I think it's available when changing
path => $self->path || [ $c->path_to('root') ], at your code to
path => $self->path || [ $c->stash('additional_template_paths')] || [$c->path_to('root')],

May be other solution exists, let me know.

header/footer

no option to provide a header or footer option to xslate.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.