Plex - [list] Users that watch the show/season/episode comparison fails when comparing to a list.

[themarkwilliams]

Describe the bug
Evaluation of "Using Plex - [list] Users that watch the show/season/episode" equal to a list is incorrect when more than one value is in the second value list.

To Reproduce
Rule conditions:
Operator: Or
First Value: Plex -[list] Users that watch show/season/episode
Action: Equals
Second Value: Text
Custom Value: ["user1", "user2"]

Expected behavior
Both users should appear in the results from First Value Result. i.e. ["user1","user2"] for it to evaluate to true. Currently, if one appears in the the First Value results, it will evaluate to true.

Screenshots
If applicable, add screenshots to help explain your problem.

Device (please complete the following information):

• OS: Ubuntu
• Version 2.4

Additional context
Test media results:
- operator: OR
action: equals
firstValueName: Plex - [list] Users that watch the show/season/episode
firstValue:
- user1
secondValueName: text
secondValue:
- user1
- user2
result: true

Using Contains (Exact list match) as the action yields the same results.

[benscobie]

This is the correct behavior, see the docs: https://docs.maintainerr.info/Rules/#list-examples

If you'd like another operator that does what you describe, raise a feature request here: https://features.maintainerr.info/

[themarkwilliams]

Apologies for a follow up, but I'm not tracking.

If I'm doing an equals comparison, and firstValue doesn't equal secondValue, how is that not a bug?

Why does this example in your list documentation evaluate to true when first value is not an exact match of secondValue?

If the operator were equals in that example, the result should be false.

Or what am I missing?

[ydkmlt84]

If you want to come on over to the Discord I can try to help you understand.

[benscobie]

Or what am I missing?

It's an exact string match of ANY item in your list, not all of the provided list values. AND vs OR. The order does not matter.

You could add another rule to match the second value in your list.

When we add the logic you want we should come up with some better descriptions for sure.

[themarkwilliams]

Got it. Any, not All for the Contains (Exact).

Should there be a behavior difference for Equals vs Contains (Exact)?

I'll try the additional, separate rule as a workaround for the multiple checks.

The All comparison would be very nice to have and I agree there is an opportunity to clarify the descriptions.

Thanks for the help!

[benscobie]

Should there be a behavior difference for Equals vs Contains (Exact)?

For arrays, equals checks that every element in firstValue is in the secondValue array (case insensitive). It's not a perfect equals, as the secondValue array could contain a value not within firstValue and it would pass.