From 99b9b3e272ae7bd8661f122f0ef284ffebce2b27 Mon Sep 17 00:00:00 2001
From: Guillem Jover <gjover@sipwise.com>
Date: Tue, 19 Jun 2018 15:29:41 +0200
Subject: [PATCH] TT#38005 Allow includes within stringy eval in perlcritic

Using stringy eval to handle conditional use is one of the few cases
where it seems to be always legitimate to allow it. This is at least
currently required for ngcp-panel.

Change-Id: Id641b87609c916e6e60dfa76d95e996fa18eef7f
---
 t/tap-tests-docker/perlcriticrc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/t/tap-tests-docker/perlcriticrc b/t/tap-tests-docker/perlcriticrc
index a984b1a..df9de1c 100644
--- a/t/tap-tests-docker/perlcriticrc
+++ b/t/tap-tests-docker/perlcriticrc
@@ -17,7 +17,7 @@ severity = 4
 
 # Use Module::Runtime for includes
 [BuiltinFunctions::ProhibitStringyEval]
-allow_includes = 0
+allow_includes = 1
 
 [CodeLayout::ProhibitQuotedWordLists]
 severity = 4