I do it that way (pretty ugly, i know), but agree, it's annoying and
I'll be much happier if Mojolicious::Plugin::Config will do deep merge
my $t = Test::Mojo->new('App');
my $config = $t->app->config;
... do something with config;
undef $t;
$t = Test::Mojo->new('App', $config);
... do
Test::Mojo allows setting the config at initialization, but the way
Mojolicious::Plugin::Config works, that doesn't allow the programmed
defaults to get picked up, which means that it is necessary to define a
complete configuration during testing. Is that more desirable than
allowing the defaults
Very interesting approach to addressing the issue, thank you for sharing!
On Tue, Apr 21, 2020 at 10:38 AM Илья wrote:
> I do it that way (pretty ugly, i know), but agree, it's annoying and I'll
> be much happier if Mojolicious::Plugin::Config will do deep merge
>
> my $t =
