- Issue created by @prudloff
- Merge request !12Issue #3415917: The current_entity property was removed in 3.0 → (Open) created by prudloff
- Status changed to Needs review
11 months ago 5:05pm 19 January 2024 Not sure why this came out with the D10 updates. Seems fine to me -- do you have someone you can get to test and mark RTBC?
- Status changed to Needs work
about 2 months ago 11:17am 31 October 2024 - 🇫🇷France prudloff Lille
We noticed it is dangerous to use this property because the entity ID is not always added to the cache keys (
eva_entity_view()
only adds it if the entity ID is used as view argument).
So if for example you have the same eva view on the same page but for different entities and your code uses the current_entity property to change the output of the view, the view render will only be cached once for the first entity and reused for the other entities.