# `Bylaw.Credo.Check.Ecto.NoAndInWhere`
[🔗](https://github.com/ryanzidago/bylaw/blob/v0.1.0-alpha.1/lib/bylaw/credo/check/ecto/no_and_in_where.ex#L1)

## Basics

> #### This check is disabled by default. {: .neutral}
>
> [Learn how to enable it](`e:credo:config_file.html#checks`) via `.credo.exs`.

This check has a base priority of `higher` and works with any version of Elixir.

## Explanation

Split combined Ecto `where` predicates into separate `where` clauses.

## Examples

Avoid:

      User
      |> where([u], u.active and u.confirmed_at > ^cutoff)
      |> Repo.all()

Prefer:

      User
      |> where([u], u.active)
      |> where([u], u.confirmed_at > ^cutoff)
      |> Repo.all()

## Notes

Packing multiple predicates into one `where` expression makes query
composition harder. Separate clauses are easier to add, remove, reorder,
and conditionally compose with helper functions.

Each clause carries one constraint, which keeps incremental query
building clear and makes diffs smaller when a predicate changes.

This check uses static AST analysis, so it favors clear source-level patterns over runtime behavior.

## Options

This check has no check-specific options. Configure it with an empty option list.

## Usage

Add this check to Credo's `checks:` list in `.credo.exs`:

```elixir
%{
  configs: [
    %{
      name: "default",
      checks: [
        {Bylaw.Credo.Check.Ecto.NoAndInWhere, []}
      ]
    }
  ]
}
```

## Check-Specific Parameters

*There are no specific parameters for this check.*

## General Parameters

Like with all checks, [general params](`e:credo:check_params.html`) can be applied.

Parameters can be configured via the [`.credo.exs` config file](`e:credo:config_file.html`).

---

*Consult [api-reference.md](api-reference.md) for complete listing*