Question 1

How to handle custom query parameters with Inquisitor?

Accepted Answer

Define pattern-matched build_query/4 functions in your controller for specific keys, like date ranges, as shown in the README's custom handler examples. This allows you to add logic beyond simple key/value matching.

Question 2

Is Inquisitor secure for API filtering?

Accepted Answer

Yes, it's designed with security in mind; by default, it's opt-in and requires explicit whitelists or handlers, preventing unauthorized access. However, you must properly configure these safeguards to avoid vulnerabilities.

Question 3

Inquisitor vs manually building Ecto queries for filtering?

Accepted Answer

Inquisitor reduces boilerplate by structuring parameter handling, but for simple, static queries, manual Ecto might be faster. It shines in dynamic APIs where security and composability are priorities, though it adds configuration overhead.

Question 4

How to use Inquisitor outside Phoenix controllers?

Accepted Answer

Import Ecto.Query's from/1 function with warn: false in plain Elixir modules, as noted in the README. This avoids errors but requires extra setup compared to seamless Phoenix integration.

Question 5

Can Inquisitor handle nested query parameters?

Accepted Answer

Not directly out-of-the-box; it focuses on key/value pairs from web requests. For nested parameters, you'd need to write custom handlers to parse and map them to Ecto queries, which can increase complexity.

Question 6

What are alternatives to Inquisitor for Elixir?

Accepted Answer

Libraries like Scrivener or custom Ecto query builders might offer similar functionality. Inquisitor stands out for its security-first approach, but alternatives may provide more automation or different abstraction levels.

inquisitor

What is inquisitor?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions