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

Twig Extractor Fails If Any Custom Extensions Used #4

Open
darkphoenixff4 opened this issue Oct 2, 2019 · 0 comments
Open

Twig Extractor Fails If Any Custom Extensions Used #4

darkphoenixff4 opened this issue Oct 2, 2019 · 0 comments

Comments

@darkphoenixff4
Copy link

Yeah, that's basically it. Because the Twig extractor can't be passed an instance of Twig to use, it always creates one with no extensions loaded, and then throws an error if it hits any custom extension items of any kind.

I tried to get around it by copying the task itself and changing it to fetch Twig from a container so I can hand it my Laravel container to get Twig out of, but that leads to a whole new set of problems; since the PHP reader tries to include any PHP file it finds before it reads it for the functions, forcing the container to load crashes that extractor with a "duplicate class" error, because it tries to load the class, even thought the container already loaded it...

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