Skip to content

fix: allow $and nested in $or - #47

Merged
fratzinger merged 1 commit into
mainfrom
fix/allow-nested-and
Oct 24, 2026
Merged

fratzinger merged 1 commit into
mainfrom
fix/allow-nested-and

Conversation

@fratzinger

Copy link
Copy Markdown
Owner

$and was only registered as a top-level filter, so a query like

{ $or: [{ $and: [{ name: 'Alice' }, { age: 30 }] }, { name: 'Bob' }] }

failed with BadRequest: Invalid query parameter $and. It's now also registered as an operator, the same way $not already is.

Adds a test in test/query-edge-cases.test.ts that fails without the change.

🤖 Generated with Claude Code

$and was only registered as a top-level filter, so Feathers rejected it
inside an $or branch with "Invalid query parameter $and". Register it as an
operator too, like $not.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@pkg-pr-new

pkg-pr-new Bot commented Oct 24, 2026

Copy link
Copy Markdown

Open in StackBlitz

npm i https://pkg.pr.new/@fratzinger/feathers-kysely@47

commit: 4031b6b

@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Preview URL Updated (UTC)
✅ Deployment successful!
View logs
feathers-kysely 4031b6b Commit Preview URL

Branch Preview URL
Oct 24 2026, 06:59 PM

@fratzinger
fratzinger merged commit 850ea5e into main Oct 24, 2026
37 checks passed
@fratzinger
fratzinger deleted the fix/allow-nested-and branch October 24, 2026 19:01
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