Premade Applicants Filter

Premade Applicants Filter

14.7k Downloads

Semantic error when using classes

RavenDT opened this issue ยท 6 comments

commented

The following expression throws a semantic error:

image

This, of course, could be user error, but I double-checked the criteria on the wiki, and I am not sure why it's not working.

commented

There is a plural s missing on both warlocks and deathknights. Additionally, both are numbers, so you have to compare them, e.g. warlocks > 0 or deathknights > 0. It's all in the documentation, if it says different somewhere, please post a link.

commented

On the front page of the repo, README.md:

image

commented

Ah sorry you are in fact using the applicant filter! Sorry for the confusion on my side. I get so little questions about the applicant filter that I automatically assumed that you are using the other addon although your screenshot clearly shows the right addon and the issue is also in the right place.

In this case the issue is clear: your expression is not quantified. This means you will have to wrap your expression in an all or some expression. The reason for this is that all applicants are technically an applicant group that consists of a list of members. Most of the time, there is only one member in this group.

In other words: this means you will always have to make a statement about the group, not about a single member, even if there is only one applicant.

So instead of saying the applicant has to be either a warlock or deathknight, you have say "all members of the applicant group are either a warlock or a deathknight and there are no other classes present" which translates to all("warlock or deathknight")

Or you might want to say "at least one (some) member of the applicant group is a warlock or deathknight and the rest can be any class. In this case the correct expression is some("warlock or deathknight")

For applicant groups with a single applicant in it, both expressions are of course equivalent.

commented

Ahh, that makes more sense! Thank you for the clarification!

commented

I think you are mixing up Premade Groups Filter and Premade Applicants Filter. The keywords in your screenshot only apply for the second addon filtering applicants of groups.

commented

Then I guess the documentation is backwards.

The first screenshot shows I was using the singular boolean option in Premade Applicants Filter in the game, because we were filtering applicants to our raid.

The second screenshot was taken from the README.md in this repository.

dd90d9e

The corresponding section in the Premade Groups Filter shows the plurals as integers:

https://github.com/0xbs/premade-groups-filter/wiki/Keywords#members