You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 22, 2020. It is now read-only.
I've been plagued with our Drupal code getting unwieldy and bugs popping up and came across this project and I'm trying to set it up.
Right now, all my builds are failing because there are debug statements in the code. While I understand it's not nice to have that, I can't control the various debug statements from the contrib modules (i.e. views, ctools, etc). I noticed in the build.properties.default, there's a debug.php.skip setting, but when I try to use that, it doesn't skip it. I searched for debug.php.skip in build.xml and it's not in there.
Shouldn't the check-debug target have an unless in it to respect that setting?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I've been plagued with our Drupal code getting unwieldy and bugs popping up and came across this project and I'm trying to set it up.
Right now, all my builds are failing because there are debug statements in the code. While I understand it's not nice to have that, I can't control the various debug statements from the contrib modules (i.e. views, ctools, etc). I noticed in the build.properties.default, there's a
debug.php.skip
setting, but when I try to use that, it doesn't skip it. I searched for debug.php.skip in build.xml and it's not in there.Shouldn't the check-debug target have an unless in it to respect that setting?
The text was updated successfully, but these errors were encountered: