@@ -4,16 +4,15 @@ Scrutizier analysis: [ made screen and cli error messages configurable.
10+ - Fix: Error reporting level needs to be configurable through config and must not be null
1111
1212#Important Changes
13+ - 1.5.2: Configurable error messages
1314- 1.4.0: Raven configuration can now be overwritten through ZendSentry configuration if needed
14- - 1.3.0: updated raven dependency to latest (0.10.0), important security relevant changes (curl), upgrade is strongly recommended
1515- 1.2.0: supports tags, every logging action returns the Sentry event_id, Raven is registered as Service
16- - 1.0.1: updated raven dependency to latest (0.7.1), important if you run pre 7.16.2 curl
1716- 0.3.1: dedicated CLI ExceptionStrategy (credits to Mateusz Mirosławski)
1817
1918#Introduction
@@ -44,7 +43,7 @@ In your project's `composer.json` use:
4443
4544 {
4645 "require": {
47- "cloud-solutions/zend-sentry": "1.5.2 "
46+ "cloud-solutions/zend-sentry": "1.5.3 "
4847 }
4948
5049Run ` php composer.phar update ` to download it into your vendor folder and setup autoloading.
@@ -185,6 +184,12 @@ Just for the record, a copy of the actual global configuration options:
185184 */
186185 'call-existing-exception-handler' => true,
187186
187+ /**
188+ * Which errors should be reported to sentry (bitmask), e. g. E_ALL ^ E_DEPRECATED
189+ * Defaults to -1 to report all possible errors (equivalent to E_ALL in >= PHP 5.4)
190+ */
191+ 'error-reporting' => -1,
192+
188193 /**
189194 * Should exceptions be displayed on the screen?
190195 */
0 commit comments