Template warnings #2230

daleif · 2025-02-17T11:35:20Z

daleif
Feb 17, 2025

I was just wondering whether it is known that one should not enable warnings in a Mojolicious template?

#!/usr/bin/env perl
use Mojolicious::Lite -signatures;

get '/' => sub ($c) {
    $c->stash( foo => 'bar' );
    $c->render(template => 'index');
};

app->start;
__DATA__

@@ index.html.ep
% use warnings;
% layout 'default';
% title 'Welcome';
<h1>Welcome to the Mojolicious real-time web framework!</h1>
<%= $foo %>    

@@ layouts/default.html.ep
<!DOCTYPE html>
<html>
  <head><title><%= title %></title></head>
  <body><%= content %></body>
</html>

Then

perl bug get /

gives

[2025-02-17 12:32:17.32860] [1456943] [trace] [DbJIcP1MmWrV] GET "/"
[2025-02-17 12:32:17.32878] [1456943] [trace] [DbJIcP1MmWrV] Routing to a callback
[2025-02-17 12:32:17.32904] [1456943] [trace] [DbJIcP1MmWrV] Rendering template "index.html.ep" from DATA section
Warning: Use of "scalar" without parentheses is ambiguous at template index.html.ep from DATA section line 5.
[2025-02-17 12:32:17.32950] [1456943] [trace] [DbJIcP1MmWrV] Rendering template "layouts/default.html.ep" from DATA section
[2025-02-17 12:32:17.32986] [1456943] [trace] [DbJIcP1MmWrV] 200 OK (0.001255s, 796.813/s)
<!DOCTYPE html>
<html>
  <head><title>Welcome</title></head>
  <body><h1>Welcome to the Mojolicious real-time web framework!</h1>
bar    
</body>
</html>

Note the warning.

In my use case I was using use Mojo::Base -signatures; in a template because I wanted to use signatures for the callback to a Collection->each, here -signatures implies warnings.

Not quite sure what it is mad about.

kraih · 2025-02-17T13:41:18Z

kraih
Feb 17, 2025
Maintainer

Yes, it is known. Something we've been trying to fix for a very long time without much luck.

0 replies

daleif · 2025-02-17T14:56:05Z

daleif
Feb 17, 2025
Author

Could it be listed in the docs somewhere? Lars Madsen Programmør Institut for Matematik Aarhus Universitet ***@***.******@***.***>

…

________________________________ From: Sebastian Riedel ***@***.***> Sent: 17 February 2025 14:41 To: mojolicious/mojo ***@***.***> Cc: Lars Madsen ***@***.***>; Author ***@***.***> Subject: Re: [mojolicious/mojo] Template warnings (Discussion #2230) Yes, it is known. Something we've been trying to fix for a very long time without much luck. — Reply to this email directly, view it on GitHub<#2230 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AKKC6CJTGPK7YM7U7PTMRO32QHRJLAVCNFSM6AAAAABXJD373KVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMRSGQ4TQNY>. You are receiving this because you authored the thread.Message ID: ***@***.***>

0 replies

guest20 · 2025-02-18T10:42:30Z

guest20
Feb 18, 2025

@daleif Seems unlikely, but does putting the variables in parens stop the warning?

@kraih Maybe Mojo::Template could use '' . instead of scalar in the code it generates? Obviously there's already been a conversation about this I haven't seen... is there a good place to look for that?

4 replies

daleif Feb 19, 2025
Author

For now I've just added

% no warnings 'ambiguous';

to the relevant templates. Having to write <%= ($var) %> all the time would just be annoying.

guest20 Feb 19, 2025

I wasn't asking if it was a good solution, I just wanted to know if it was a solution at all. ;)

daleif Feb 20, 2025
Author

I wasn't asking if it was a good solution, I just wanted to know if it was a solution at all. ;)

With the example I posted changed with this <%= ($foo) %>, no the warning remains.

guest20 Feb 20, 2025

So it's not any kind of solution then. Understood.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Template warnings #2230

{{title}}

Replies: 3 comments 4 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

Template warnings #2230

daleif Feb 17, 2025

Replies: 3 comments · 4 replies

kraih Feb 17, 2025 Maintainer

daleif Feb 17, 2025 Author

guest20 Feb 18, 2025

daleif Feb 19, 2025 Author

guest20 Feb 19, 2025

daleif Feb 20, 2025 Author

guest20 Feb 20, 2025

daleif
Feb 17, 2025

Replies: 3 comments 4 replies

kraih
Feb 17, 2025
Maintainer

daleif
Feb 17, 2025
Author

guest20
Feb 18, 2025

daleif Feb 19, 2025
Author

daleif Feb 20, 2025
Author