A little update:
The fusion migrations were further refined via this change to be more careful when rewriting expressions and Neos 8.4 now provides the remaining runtime utilities to allow the new fusion code to work.
Sebastian and me re-evaluated today if we want to add a deprecation log for deprecated EEL Expressions in 8.4 but we decided that it would be of no gain for our users.
The log is already part of Neos 9 via FEATURE: Fusion eel neos deprecation tracer by mhsdesign · Pull Request #5262 · neos/neos-development-collection · GitHub
Following problems make the logs invaluable and impractical for Neos 8.x:
- we have no idea in the fusion runtime where the eel expression was defined as this information is not preserved
- we have not migrated our Neos.Neos package to use non deprecated apis - this is not even possible for all cases. The log is thus already swamped with logs from Neos where users have no influence.
- we would need to adjust Neos.Neos as good as possible and also other packages like Neos.Seo and give them a minor release which will be lots of work.
- we could store the information where the eel expression was defined - topic source maps in fusion - and thus ignore all logs from “Neos.*”
→ but users are in the end faced with the same problem we have and will not be able to migrate all cases likenode.context.dimensionsalready to non deprecated syntax as 8.4 lacks the replacements.
While it might be easy for a simple page to satisfy the log - a complex site has no chance to become fully 9.0 compatible and especially not with the mentioned problems above. Thus we will not backport this feature - and thus preventing to swamp our users logs;)