-
Notifications
You must be signed in to change notification settings - Fork 181
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Backported display_errors-handling to sf1 #328
Backported display_errors-handling to sf1 #328
Conversation
c008cca
to
bed4638
Compare
Looks like php-cs-fixer rules require me to change something in the class although I haven't touched it? |
@thirsch Unfortunately, the cs-fixer is not smart enough. It can't just look at the syntax in the PR patch. On the other hand, it seems that the original intention of the current cs-fixer setting to search only in files affected by PR has been lost. |
The location marked by the cs-fixer is incorrect. That's the problem anyway: --- /Users/connor/Work/FriendsOfSymfony1/symfony1/lib/config/sfApplicationConfiguration.class.php
+++ /Users/connor/Work/FriendsOfSymfony1/symfony1/lib/config/sfApplicationConfiguration.class.php
@@ -129,13 +129,13 @@
// error settings
if (!in_array(PHP_SAPI, array('cli', 'phpdbg', 'embed'), true)) {
- ini_set('display_errors', 0);
+ ini_set('display_errors', 0);
} elseif (
!filter_var(ini_get('log_errors'), FILTER_VALIDATE_BOOLEAN)
|| ini_get('error_log')
) {
- // CLI - display errors only if they're not already logged to STDERR
- ini_set('display_errors', 1);
+ // CLI - display errors only if they're not already logged to STDERR
+ ini_set('display_errors', 1);
}
error_reporting(sfConfig::get('sf_error_reporting'));
|
bed4638
to
8bdc953
Compare
Thanks and sorry, must have been to late yesterday. No idea, why I used 2 instead of 4 spaces for the three lines. |
8bdc953
to
de31a26
Compare
de31a26
to
b2097d5
Compare
Found it, our fork seems to use a pre-php-cs-fixer version with two instead of four spaces and I initially implemented it there. |
Two spaces? 😱 What an evil company!? |
b2097d5
to
9ce2dcb
Compare
Hi @thePanz, this (and FriendsOfSymfony1/doctrine1@eeb1777) were the last changes I need to go back to the "official" release packages. Any plans for a new release of doctrine1 and symfony1? I'd like to avoid using dev-Tags on production system. |
yes, I think we can tag the next releases 👍 Done!
|
One year nothing, now 2 versions in 2 weeks. A huge tempo. |
People asked, we delivered 😅
That's a good way to push for fixes? 😀 |
This pr is a follow-up to #239.
Thanks for your review in the other pr, @alquerci. I tried to remember what we wanted to fix with it and it turns out, we never used the setting for any other value than "Off". Therefore the semantic we need is the same as what current symfony is doing.
The main reason for this change is to keep the results (especially ajax and api calls) clean from notices and warnings.
As I closed the other pr with deleting the branch on our fork quite some time ago, I had to create a new one.