Marcus Bolmstedt

Hi David, I didn't really think about how the generated function for 7.4 might look like, but it looks like it would be fully backwards compatible. The best solution here...

This error message is correct. foo() is a constructor, it just doesn't run. If you would remove __construct() it would start to run, which would be quite unexpected and dangerous....

Yes, you are correct, this violation should not be given. However, another violation, with different wording, should be. Something like "Classes should not have a method with the same name...

Fixed by #2591.

This bug seems to still be unresolved in 1.7.1. When I run a rule for movies present in 0 other collections, it adds a movie that matches the rest of...

Actually, it is still happening, but for a second movie, not the first. I believe it might be related to the cached metadata not being updated correctly, or something. This...

Sorry for the delay, but here is what I'm seeing. This is for an item that stays in the collection between runs: ``` - plexId: 10711 result: false sectionResults: -...

Adding that additional rule gives some interesting insight, I think: For the item (`10711`) that always stays in the collection: ``` ... - operator: AND action: equals firstValueName: Plex -...

> @bolmstedt, PR #801 might fix your issue. Once merged, you should be able to try it out with the latest develop/main image. Tried the latest develop image, and although...

Exactly, "Leaving soon" is the name of the custom collection related to that ruleset. All mentioned shifting items are being added and removed from that collection. I realise now that...