Skip to content

fix: reject ordering operators on boolean/binary attributes during validation#200

Merged
q-uint merged 1 commit into
masterfrom
fix/validate-operator-type-compatibility
Mar 26, 2026
Merged

fix: reject ordering operators on boolean/binary attributes during validation#200
q-uint merged 1 commit into
masterfrom
fix/validate-operator-type-compatibility

Conversation

@q-uint
Copy link
Copy Markdown
Collaborator

@q-uint q-uint commented Mar 26, 2026

Validate() only checked attribute path existence, not type-operator compatibility. Filters like active gt true passed validation despite RFC 7644 Section 3.4.2.2 requiring a 400 response for boolean/binary attributes with gt, lt, ge, or le operators.

Summary

  • Validate() only checked attribute path existence, not type-operator compatibility
  • Filters like active gt true passed validation despite RFC 7644 S3.4.2.2 requiring a 400 response for boolean/binary attributes with ordering operators (gt, lt, ge, le)
  • Added validateOperator() to reject these at validation time, not just during PassesFilter() evaluation

…lidation

Validate() only checked attribute path existence, not type-operator
compatibility. Filters like `active gt true` passed validation despite
RFC 7644 Section 3.4.2.2 requiring a 400 response for boolean/binary
attributes with gt, lt, ge, or le operators.
@q-uint q-uint self-assigned this Mar 26, 2026
@q-uint q-uint merged commit cd9a605 into master Mar 26, 2026
8 checks passed
@q-uint q-uint deleted the fix/validate-operator-type-compatibility branch March 26, 2026 13:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant