-
-
Notifications
You must be signed in to change notification settings - Fork 67
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
Conflicts with Symfony Deprecation detector #9
Comments
This was caused by See: acquia/blt@4fe4cbe |
To be clear -- the issue was caused when running a Drupal project with BLT 9. |
We will be removing |
@mikemadison13 I've read through that thread and others and that PR seems to need quite a bit of work. Can you elaborate on when "the very near future" may be? |
@JDDoesDev it's pretty high on my priority list, so in the next couple of days. i don't think removing it will be terribly hard, since BLT 10x doesn't have an analog to this feature (we'll just be removing it outright from 9.2.x). We may "re-add" something else in the future, but my hope is to yank this out so people can start doing the deprecation scans ASAP. |
@mikemadison13 acquia/blt#3546 seems to be a good place to meet in the middle so that people still have a command line option and aren't tied to the UI. This is definitely a BLT problem and not drupal-check problem. |
FYI the fix is up in a PR on BLT's queue now. |
In debugging at MidCamp we had issues where the tool would not run. The site had Symfony Deprecation Detector which was requiring 3.1
The text was updated successfully, but these errors were encountered: