Acme-CPANModulesBundle-Import-MojoliciousAdvent-2018

 view release on metacpan or  search on metacpan

devdata/https_mojolicious.io_blog_2018_12_04_testing-hooks-and-helpers_  view on Meta::CPAN

<pre><code>#!/usr/bin/env perl
use Mojolicious::Lite;
# Allow access via tokens
plugin Config =&gt; {
    default =&gt; {
        tokens =&gt; { }, # token =&gt; username
    },
};
helper current_user =&gt; sub( $c ) {
    my $auth = $c-&gt;req-&gt;headers-&gt;authorization;
    return undef unless $auth;
    my ( $token ) = $auth =~ /^Token\ (\S+)$/;
    return undef unless $token;
    return $c-&gt;app-&gt;config-&gt;{tokens}{ $token };
};
</code></pre>

<p>Then, rather than generating web requests to check all our
authentication edge cases, I can build a controller and set the right
headers to run my tests (using <a href="https://mojolicious.org/perldoc/Test/Mojo#new">Test::Mojo configuration
overrides</a> to add a test
token):</p>

devdata/https_mojolicious.io_blog_2018_12_04_testing-hooks-and-helpers_  view on Meta::CPAN

use Test::More;
use Test::Mojo;
use Mojo::File qw( path );
my $token = 'mytoken';
my $t = Test::Mojo->new( path('myapp.pl'), {
    # Add a token as a configuration override
    tokens => { $token => 'preaction' },
} );

my $c = $t->app->build_controller;
is $c->current_user, undef, 'current_user not set';

$c->req->headers->authorization( 'NOTATOKEN' );
is $c->current_user, undef, 'current_user without "Token"';

$c->req->headers->authorization( 'Token NOTFOUND' );
is $c->current_user, undef, 'current_user token incorrect';

$c->req->headers->authorization( "Token $token" );
is $c->current_user, 'preaction', 'current_user correct';
</code></pre>

<p>Of course, we&#39;ll still need to test whether the routes we want to
protect with tokens are protected, but this shows that our
authentication helper works so if there are problems with our routes,
it&#39;s probably not here.</p>

devdata/https_mojolicious.io_blog_2018_12_11_who-watches-the-minions_  view on Meta::CPAN

  "children" => [],
  "created" => "2018-11-23T19:15:47Z",
  "delayed" => "2018-11-23T19:15:47Z",
  "finished" => "2018-11-23T19:15:48Z",
  "id" => 1,
  "notes" => {},
  "parents" => [],
  "priority" => 0,
  "queue" => "default",
  "result" => "0.0716841220855713",
  "retried" => undef,
  "retries" => 0,
  "started" => "2018-11-23T19:15:47Z",
  "state" => "finished",
  "task" => "check_url",
  "worker" => 1
}
</code></pre>

<p>But, it&#39;d be a lot nicer if I didn&#39;t have to open a terminal, open an
SSH connection, and run a command to look at the status of my Minion.</p>

devdata/https_mojolicious.io_blog_2018_12_16_browser-diet_  view on Meta::CPAN

JavaScript is downloading.  These two
<a href="https://flaviocopes.com/javascript-async-defer/">wise</a>
<a href="https://bitsofco.de/async-vs-defer/">owls</a>
can help decide which one to use.</p>

<p>Tell your script to load after the main page
with this
<a href="https://mojolicious.org/perldoc/Mojolicious/Plugin/TagHelpers#javascript">tag helper</a>
in your template</p>

<pre><code>%= javascript &#39;/js/lib/jquery.min.js&#39;, defer =&gt; undef
</code></pre>

<p>which produces</p>

<pre><code>&lt;script defer src=&quot;/path/to/script.js&quot;&gt;&lt;/script&gt;
</code></pre>

<p>If you want it in the <code>&lt;head&gt;</code>, you&#39;ll have to put it in your layout
otherwise the template will do.</p>