-
Notifications
You must be signed in to change notification settings - Fork 250
Description
The latest version of this package conflicts in composer with the Twig version I currently have, however I have no intention of using the Twig integration. I presume the conflict marker is there due to version support for the Twig bridge rather than a genuine code conflict, so it seems bad that I'm prevented from using your package because of this? Upgrading Twig in my project will be a huge undertaking at the moment because of the network of dependencies that are tied in to it currently.
Is there a reason for the conflict other than through use of the Twig Bridge? Perhaps the bridges could be separate wrapper packages that can be optionally installed, meaning I only require and download them when I need them, leaving the core behaviour isolated?