Weird. I haven’t noticed that before but will see if I can reproduce when I have a moment. Thanks for the comment!

Absolutley! We had the m2m use case for what we implemented so we built that wrapper to create the needed array of UC’s from that data model. If you just need to pass in a UC you could use _matchesUCList() directly. The “_” prepending the function name is typically used to indicate a function intended for internal use only (by other functions in that object)…but that is just a convention, so you could use it directly as-is or rename it to remove the “_” (and make the updates throughout the rest of the code) and use it that way. Thanks for your comments!

Thanks for catching this Dorian! I believe I’ve fixed them, but let me know if you see anything else askew!

Question: So this wrapper currently makes an assumption that you need to have another custom table that holds the m2m data right? I wonder if you can skip the idea of having an extra table to hold that and just pass in an existing User Criteria.

So for example:
In KB you have the “Can Read” where you add all the UCs that “Can Read”.

What if you just had a function that takes in a given UC record, evaluates if the user matches thes the criteria. That would save you from having to create m2m tables right? In cases where you need more than 1 UC to be evaluated, you just loop through the function you created and return true if any match.

On line 94 “this._matchesList(ucArray, emptyListReturn);”
On line 110: “return this.matchesList(ucArrayofOne, false);”,

I believe that you renamed the function to “_matchesUCList” so those function calls need to be renamed.