-
Notifications
You must be signed in to change notification settings - Fork 83
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
Unneeded Symfony/Yaml dependency? (and bundled dev dependencies) #247
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Further activity such as? |
I think it's only used in a single test (
This relates to #304 a little but this yaml dep is causing us a few problems which I think can be easily resolved. Thanks! |
Every time I want to clear the object cache I have to disable this plugin due to this issue...obviously it's not all about me, but any movement on this seemingly small change would be greatly appreciated 🙏 . If you specify which is your favoured approach I'm more than happy to provide a PR 😇 |
I actually don't think this will help because the autoloader won't change which is where the problem lies, so can rule that one out Another option though is to use https://github.com/coenjacobs/mozart this is used by some major plugins already, |
if i understand the issue correctly here, i think this has been fixed since 4.1.0. feel free to let me know if it isn't addressed for you and we can revisit. |
While 4.10 removed the other bundled dev dependencies, |
thanks for confirming! do you want to take a pass at addressing this? |
I took a shot at it in #374. |
Fix #247 - unneeded symfony/yaml dependency
I've been running into some problems with a wp-cli command that needs a newer version of Symfony/Yaml than is vendored with this plugin, and this plugin ends up blocking it from being loaded because of autoloader precedence.
However, I can't seem to find where the Yaml component is actually used by anything within the Cloudflare plugin, so the dependency appears redundant. (In addition, the bundled vendor/ directory appears to have been built with development dependencies, meaning the distribution is unnecessarily large and prone to overriding other packages with outdated versions as well.)
Perhaps symfony/yaml can now be removed from composer.json and the vendor tree rebuilt with just the non-development dependencies? Thanks.
The text was updated successfully, but these errors were encountered: