This is achieved with a lazy default for `conditions[:count]`.
The function `Query.count/1` must now be used to get the effective count condition.

Alternative would have been to continue setting `count` to a
non `nil` default when conditions are first built. This has the inconvenient
of not being to distinguish a count set by default from an explicit one (i.e.
`Query.css(".x") |> Query.at(0)` from `Query.css(".x", count: 1) |> Query.at(0)`)

[Fixes elixir-wallaby#641]

This is achieved with a lazy default for `conditions[:count]`.
The function `Query.count/1` must now be used to get the effective count condition.

Alternative would have been to continue setting `count` to a
non `nil` default when conditions are first built. This has the inconvenient
of not being to distinguish a count set by default from an explicit one (i.e.
`Query.css(".x") |> Query.at(0)` from `Query.css(".x", count: 1) |> Query.at(0)`)

[Fixes elixir-wallaby#641]

This is achieved with a lazy default for `conditions[:count]`.
The function `Query.count/1` must now be used to get the effective count condition.

Alternative would have been to continue setting `count` to a
non `nil` default when conditions are first built. This has the inconvenient
of not being to distinguish a count set by default from an explicit one (i.e.
`Query.css(".x") |> Query.at(0)` from `Query.css(".x", count: 1) |> Query.at(0)`)

[Fixes elixir-wallaby#641]

This is achieved with a lazy default for `conditions[:count]`.
The function `Query.count/1` must now be used to get the effective count condition.

Alternative would have been to continue setting `count` to a
non `nil` default when conditions are first built. This has the inconvenient
of not being to distinguish a count set by default from an explicit one (i.e.
`Query.css(".x") |> Query.at(0)` from `Query.css(".x", count: 1) |> Query.at(0)`)

[Fixes elixir-wallaby#641]

This is achieved with a lazy default for `conditions[:count]`.
The function `Query.count/1` must now be used to get the effective count condition.

Alternative would have been to continue setting `count` to a
non `nil` default when conditions are first built. This has the inconvenient
of not being to distinguish a count set by default from an explicit one (i.e.
`Query.css(".x") |> Query.at(0)` from `Query.css(".x", count: 1) |> Query.at(0)`)

[Fixes elixir-wallaby#641]

This is achieved with a lazy default for `conditions[:count]`.
The function `Query.count/1` must now be used to get the effective count condition.

Alternative would have been to continue setting `count` to a
non `nil` default when conditions are first built. This has the inconvenient
of not being to distinguish a count set by default from an explicit one (i.e.
`Query.css(".x") |> Query.at(0)` from `Query.css(".x", count: 1) |> Query.at(0)`)

[Fixes elixir-wallaby#641]

This is achieved with a lazy default for `conditions[:count]`.
The function `Query.count/1` must now be used to get the effective count condition.

Alternative would have been to continue setting `count` to a
non `nil` default when conditions are first built. This has the inconvenient
of not being to distinguish a count set by default from an explicit one (i.e.
`Query.css(".x") |> Query.at(0)` from `Query.css(".x", count: 1) |> Query.at(0)`)

[Fixes elixir-wallaby#641]

This is achieved with a lazy default for `conditions[:count]`.
The function `Query.count/1` must now be used to get the effective count condition.

Alternative would have been to continue setting `count` to a
non `nil` default when conditions are first built. This has the inconvenient
of not being to distinguish a count set by default from an explicit one (i.e.
`Query.css(".x") |> Query.at(0)` from `Query.css(".x", count: 1) |> Query.at(0)`)

[Fixes elixir-wallaby#641]

This is achieved with a lazy default for `conditions[:count]`.
The function `Query.count/1` must now be used to get the effective count condition.

Alternative would have been to continue setting `count` to a
non `nil` default when conditions are first built. This has the inconvenient
of not being to distinguish a count set by default from an explicit one (i.e.
`Query.css(".x") |> Query.at(0)` from `Query.css(".x", count: 1) |> Query.at(0)`)

[Fixes elixir-wallaby#641]

This is achieved with a lazy default for `conditions[:count]`.
The function `Query.count/1` must now be used to get the effective count condition.

Alternative would have been to continue setting `count` to a
non `nil` default when conditions are first built. This has the inconvenient
of not being to distinguish a count set by default from an explicit one (i.e.
`Query.css(".x") |> Query.at(0)` from `Query.css(".x", count: 1) |> Query.at(0)`)

[Fixes elixir-wallaby#641]

This is achieved with a lazy default for `conditions[:count]`.
The function `Query.count/1` must now be used to get the effective count condition.

Alternative would have been to continue setting `count` to a
non `nil` default when conditions are first built. This has the inconvenient
of not being to distinguish a count set by default from an explicit one (i.e.
`Query.css(".x") |> Query.at(0)` from `Query.css(".x", count: 1) |> Query.at(0)`)

Fixes #641