feat(api): define filter limits in openapi spec

[tothandras]

Summary by CodeRabbit

• New Features
  • Added validation constraints to array-based filter operations, enforcing minimum and maximum item limits to ensure valid filter requests and prevent malformed queries.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

Added @minItems and @maxItems validation annotations to array-typed filter properties in the TypeSpec filter definition file, enforcing item count constraints (1-100 for $in/$nin, 1-10 for $and/$or) across five filter model types.

Changes

Cohort / File(s)	Summary
Filter validation constraints api/spec/src/filter.tsp	Added @minItems and @maxItems annotations to array properties: $in and $nin now enforce 1–100 items, while $and and $or enforce 1–10 items. Applied across FilterString, FilterIDExact, FilterInteger, FilterFloat, and FilterTime models.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: adding filter limits (minItems/maxItems constraints) to the OpenAPI specification for filter properties.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feat/api-improvements

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}