From b3f67a16094168cc334f5da93a86f09476e01601 Mon Sep 17 00:00:00 2001
From: xXx-caillou-xXx
Date: Thu, 30 Aug 2018 15:02:22 +0200
Subject: Change how we're handling invalid configurations

Since our configuration format is a bit more complex than php's one,
we have a `sp.allow_broken_configuration` parameter (`false` by default),
that you can set to `true` if you want PHP to carry on if your Snuffleupagus'
configuration contains syntax errors. You'll still get a big scary message in
your logs of course. We do **not** recommend to use it of course, but sometimes
it might be useful to be able to "debug in production" without breaking your
website.---
 src/tests/broken_conf_config_regexp.phpt | 3 +++
 1 file changed, 3 insertions(+)

(limited to 'src/tests/broken_conf_config_regexp.phpt')

diff --git a/src/tests/broken_conf_config_regexp.phpt b/src/tests/broken_conf_config_regexp.phpt
index c4e788e..2977e3a 100644
--- a/src/tests/broken_conf_config_regexp.phpt
+++ b/src/tests/broken_conf_config_regexp.phpt
@@ -12,3 +12,6 @@ PHP Fatal error:  [snuffleupagus][config] '.filename_r()' is expecting a valid r
 Fatal error: [snuffleupagus][config] Failed to compile '*.': %s on line 1. in Unknown on line 0
 
 Fatal error: [snuffleupagus][config] '.filename_r()' is expecting a valid regexp, and not '"*."' on line 1 in Unknown on line 0
+
+Fatal error: [snuffleupagus][config] Invalid configuration file in Unknown on line 0
+Could not startup.
-- 
cgit v1.3