Skip to content

Do not lazy load CompilingEvaluator#21

Open
soee wants to merge 1 commit into
mocdk:masterfrom
soee:master
Open

Do not lazy load CompilingEvaluator#21
soee wants to merge 1 commit into
mocdk:masterfrom
soee:master

Conversation

@soee

@soee soee commented Apr 30, 2024

Copy link
Copy Markdown

In Neos 9 we have exception thrown due to wrong argument type when caliing Utility::evaluateEelExpression().
The expected type is EelEvaluatorInterface but the unresolved dependency injection is used instead.
This commit marks the eelEvaluator propery as not be lazy loaded while injecting.

@mhsdesign mhsdesign left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oddd ... that should be also a problem in 8 and 7 ...

@dlubitz

dlubitz commented May 1, 2024

Copy link
Copy Markdown

Hmm, I use it in Neos 7 and 8 and have no issues.

@mhsdesign

Copy link
Copy Markdown

The fusion runtime also has to do this since ages as this is imo not a regression but a well known flaw which is also documented:

https://github.com/neos/neos-development-collection/blob/6af1939bb5dac41e58475f848cb90e4b82493e87/Neos.Fusion/Classes/Core/Runtime.php#L727-L731

see _activateDependency part in https://flowframework.readthedocs.io/en/7.3/TheDefinitiveGuide/PartIII/ObjectManagement.html#lazy-dependency-injection

@mikec655

Copy link
Copy Markdown

After upgrading to Neos 9, I'm getting the same exception. But only for some images it seems. I too didn't experienced this problem in Neos 7/8. Is there any update for this PR?

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

Successfully merging this pull request may close these issues.

4 participants