Issue

Patch validation errors get swallowed up to ScimErrorInvalidValue here:

Example

Hence, the ScimType for errors upon patch validation is not always respected, for example:

    { "schemas":
           ["urn:ietf:params:scim:api:messages:2.0:PatchOp"],
         "Operations":[
           {
            "op":"remove",
            "path":"",
            "value":"newusername"
           }]
    }

In this example, a remove path must be provided and as per the RFC and we should return a scimType of noTarget:

If "path" is unspecified, the operation fails with HTTP status code 400 and a "scimType" error code of "noTarget".

Although the code does actually do this validation here

The same issue is seen for other validations (e.g. sometimes a SyntaxError is swallowed).