Skip to content
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 Twig #256

Open
chrisemerson opened this issue Jan 19, 2020 · 0 comments
Open

Conflicts with Twig #256

chrisemerson opened this issue Jan 19, 2020 · 0 comments

Comments

@chrisemerson
Copy link

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant