You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unassigned attributes, the null value, or an empty array (in the case
of a multi-valued attribute) SHALL be considered to be equivalent in
"state". Assigning an attribute with the value "null" or an empty
array (in the case of multi-valued attributes) has the effect of
making the attribute "unassigned". When a resource is expressed in
JSON format, unassigned attributes, although they are defined in
schema, MAY be omitted for compactness.
However, current validator doesn't respect this, so we gotta strip away all attributes with null values to satisfy this validator, which represent extra work.
The text was updated successfully, but these errors were encountered:
ostrolucky
added a commit
to eqsgroup/scim-schema
that referenced
this issue
Oct 25, 2024
According RFC 7643, section 2.5
However, current validator doesn't respect this, so we gotta strip away all attributes with null values to satisfy this validator, which represent extra work.
The text was updated successfully, but these errors were encountered: