# `AshGrant.FieldFilterCheck`
[🔗](https://github.com/jhlee111/ash_grant/blob/v0.22.0/lib/ash_grant/checks/field_filter_check.ex#L1)

Per-record field-group visibility check (issue #117 phase ②).

An `Ash.Policy.FilterCheck` used inside Ash `field_policies`. For a required
field group, `filter/3` returns a per-row predicate — `false` (the group's
fields are `%Ash.ForbiddenField{}` on every row), `true` (visible on every
row), or an Ash expression (visible only on rows matching the contributing
grants' scope / instance ids). Ash compiles the predicate into a per-row
calculation, so a field can be visible on some records and forbidden on others
in the same result set.

This is the per-record counterpart to the action-wide `AshGrant.FieldCheck`
(a `SimpleCheck`). It reuses `AshGrant.Evaluator.field_group_grants/5` to find
the allow grants that reach the required group (including instance permissions
and inheritance), then builds the predicate exactly like `AshGrant.FilterCheck`
builds row filters.

# `auto_filter`

# `auto_filter_not`

# `check`

# `eager_evaluate?`

# `expand_description`

# `field_filter_check`

Builds the check tuple for a required field group, for use in a `field_policy`.

# `field_visibility_filter`

Builds the per-row visibility predicate for `required_group` from `permissions`.

Returns `false` (forbidden on every row), `true` (visible on every row), or an
Ash expression (visible only on rows matching the contributing grants' scope /
instance ids). Exposed for testing.

# `init`

# `prefer_expanded_description?`

# `reject`

# `requires_original_data?`

# `strict_check`

# `strict_check_context`

# `type`

---

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