Path with a complex filter match only the first occurrence about scim-patch HOT 3 CLOSED

I gave only a look and i think this is caused by the navigate function that return only a single resource instead of a list of them. I've forked the project and in these days i will try some solutions.

from scim-patch.

Hey @leonardo-speranzon this is a good catch, and I am not sure how to solve it.
Have you look at the code yourself? Would you be open for a contribution on this?

I will try to look at it as soon as I have a bit more time, but I don't have a lot of time for now unfortunately.

from scim-patch.

I also found out that in the case of patch {op: "replace", value: {newProperty: "post"}, path: "emails"} on resource like this

{
    ...
    emails: [
        { value: "[email protected]", primary: true, newProperty: "pre"},
        { value: "[email protected]", primary: false, newProperty: "pre" },
    ]
    ...
}

act like an add and simply push a new element {newProperty: "post"} to the emails array.

Instead the "equivalent" patch {op: "replace", value: "post", path: "emails.newProperty"} add the newProperty property directly to the array (JS magic lol).

I think the correct behavior for both of them is to change the newProperty property in all of the existing emails.
The RFC say:

   o  If the target location is a multi-valued attribute and no filter
      is specified, the attribute and all values are replaced.

I should open a related issue or i can do it in the same PR?

from scim-patch.