Duplicate rows for some entities with multiple entity references

apkwilson → changed the visibility of the branch 3452532-duplicate-rows-for to hidden.

apkwilson → changed the visibility of the branch 3452532-duplicate-rows-for to active.

apkwilson → changed the visibility of the branch 3452532-duplicate-rows-for to hidden.

Works for me and is simple enough. Thanks!

Probably overkill but I want to get more tests in this module so getting the ball rolling here. Thanks for this, fix btw @apkwilson, it fixes a problem for me with date_recur I was seeing as well, so I will commit it really soon!

joelpittet → changed the visibility of the branch 8.x-1.x to hidden.

Moved the duplicate-check logic into a new instance-based isEntityAlreadyRendered($id) method. This change was motivated by two goals:

1. Making the code much easier to test.
2. Simplifying the render() method by removing internal static logic.

Test highlights

1. First call with an ID → false
2. Second call with the same ID → true
3. New ID resets correctly → false, then true
4. Calling the first ID again later → true, confirming we now track all previously rendered IDs—not just the last one, which was the regression we fixed.

Real‑world verification
I manually reverted to the old static-based logic inside isEntityAlreadyRendered() and confirmed the last assertion failed. I also tested with a real date_recur scenario—this solution behaves identically to the static version but is hopefully easier to maintain and test.

I manually reverted to the old static-based logic inside isEntityAlreadyRendered() and confirmed the last assertion failed. I also tested with a real date_recur scenario—this solution behaves identically to the static version but is cleaner and easier to maintain and test.

I've committed this to the dev branch for hopefully a quick release, thanks again @apkwilson and @daniel korte for bring this issue up and finding a solution!