View Source PhoenixApiToolkit.Ecto.Validators (Phoenix API Toolkit v3.1.2)
Generic validators and helper functions for validating Ecto changesets.
examples
Examples
The examples in this module use the following basic schema and changeset:
@schema %{
first_name: :string,
last_name: :string,
last_name_prefix: :string,
order_by: :string,
file: :string,
mime_type: :string
}
def changeset(changes \\ %{}) do
{%{}, @schema} |> cast(changes, [:first_name, :last_name, :order_by, :file])
end
Link to this section Summary
Functions
If the changeset does not contain a change for field
- even if the field already
has a value in the changeset data - set it to change
. Useful for setting default changes.
If changeset
is valid, apply the first function then_do
to it,
else apply the second function else_do
to it, which defaults to the
identity function.
Move a change to another field in the changeset (if its value is not nil).
Like Ecto.Changeset.put_change/3
, the change is moved without additional validation.
Optionally, the value can be mapped using value_mapper
, which defaults to the identity function.
Apply function
to multiple fields of the changeset.
Convenience wrapper for validators that don't support multiple fields.
Validates that field
is a suitable parameter for an (i)like query.
Validate the value of an order_by
query parameter. The format of the parameter
is expected to match ~r/^(asc|desc|asc_nulls_last|desc_nulls_last|asc_nulls_first|desc_nulls_first):(\w+)$/
(may be repeated, comma-separated).
The supported fields should be passed as a list or MapSet
(which performs better) to orderables
.
Validates that field
(or multiple fields) contains plaintext.
Validate a searchable field. If the value of field
is postfixed with '*',
a fuzzy search instead of a equal_to match is considered to be intended. In this case, the value
must be at least 4 characters long and must be (i)like safe (as per validate_ilike_safe/2
),
and is moved to search_field
. The postfix '*' is stripped from the search string.
For verifying files uploaded as base64-encoded binaries. Attempts to decode field
and
validate its file signature. The file signature, also known as a file's "magic bytes",
can be looked up on the internet (for example here)
and may be a list of allowed magic byte types.
Like validate_upload/3
, but sets the mime type to mime_field
. Parameter
file_sig_mime_map
should be a map of file type signatures to mime types.
Link to this section Functions
@spec default_change(Ecto.Changeset.t(), atom(), any()) :: Ecto.Changeset.t()
If the changeset does not contain a change for field
- even if the field already
has a value in the changeset data - set it to change
. Useful for setting default changes.
examples
Examples
For the implementation of changeset/1
, see Elixir.PhoenixApiToolkit.Ecto.Validators
.
iex> changeset() |> default_change(:first_name, "Peter")
#Ecto.Changeset<action: nil, changes: %{first_name: "Peter"}, errors: [], data: %{}, valid?: true>
iex> changeset(%{first_name: "Jason"}) |> default_change(:first_name, "Peter")
#Ecto.Changeset<action: nil, changes: %{first_name: "Jason"}, errors: [], data: %{}, valid?: true>
@spec map_if_valid( Ecto.Changeset.t(), (Ecto.Changeset.t() -> any()), (Ecto.Changeset.t() -> any()) ) :: Ecto.Changeset.t()
If changeset
is valid, apply the first function then_do
to it,
else apply the second function else_do
to it, which defaults to the
identity function.
examples
Examples
# function then_do is applied to the changeset if it is valid
iex> %Ecto.Changeset{valid?: true} |> map_if_valid(& &1.changes)
%{}
# if the changeset is invalid and else_do is provided, apply it to the changeset
iex> %Ecto.Changeset{valid?: false} |> map_if_valid(& &1.changes, & &1.errors)
[]
# else_do defaults to identity, returning the changeset
iex> %Ecto.Changeset{valid?: false} |> map_if_valid(& &1.changes)
#Ecto.Changeset<action: nil, changes: %{}, errors: [], data: nil, valid?: false>
@spec move_change(Ecto.Changeset.t(), atom(), atom(), (any() -> any())) :: Ecto.Changeset.t()
Move a change to another field in the changeset (if its value is not nil).
Like Ecto.Changeset.put_change/3
, the change is moved without additional validation.
Optionally, the value can be mapped using value_mapper
, which defaults to the identity function.
examples
Examples
For the implementation of changeset/1
, see Elixir.PhoenixApiToolkit.Ecto.Validators
.
# there is no effect when there is no change to the field
iex> changeset() |> move_change(:first_name, :last_name)
#Ecto.Changeset<action: nil, changes: %{}, errors: [], data: %{}, valid?: true>
# a change is moved to another field name as-is by default
iex> changeset(%{first_name: "Pan"}) |> move_change(:first_name, :last_name)
#Ecto.Changeset<action: nil, changes: %{last_name: "Pan"}, errors: [], data: %{}, valid?: true>
# an optional value_mapper can be passed to do some processing on the change along the way
iex> changeset(%{first_name: "Pan"}) |> move_change(:first_name, :last_name, & String.upcase(&1))
#Ecto.Changeset<action: nil, changes: %{last_name: "PAN"}, errors: [], data: %{}, valid?: true>
@spec multifield_apply( Ecto.Changeset.t(), [atom()], (Ecto.Changeset.t(), atom() -> Ecto.Changeset.t()) ) :: Ecto.Changeset.t()
Apply function
to multiple fields of the changeset.
Convenience wrapper for validators that don't support multiple fields.
examples-doctests
Examples / doctests
For the implementation of changeset/1
, see Elixir.PhoenixApiToolkit.Ecto.Validators
.
iex> changeset(%{first_name: "Luke", last_name: "Skywalker"})
...> |> multifield_apply([:first_name, :last_name], &validate_length(&1, &2, max: 3))
...> |> Map.take([:valid?, :errors])
%{valid?: false, errors: [
{:last_name, {"should be at most %{count} character(s)", [count: 3, validation: :length, kind: :max, type: :string]}},
{:first_name, {"should be at most %{count} character(s)", [count: 3, validation: :length, kind: :max, type: :string]}}
]}
@spec validate_ilike_safe(Ecto.Changeset.t(), atom() | [atom()]) :: Ecto.Changeset.t()
Validates that field
is a suitable parameter for an (i)like query.
User input for (i)like queries should not contain metacharacters because this creates a denial-of-service attack vector: introducing a lot of metacharacters rapidly increases the performance costs of such queries. The metacharacters for (i)like queries are '_', '%' and the escape character of the database, which defaults to '\'.
examples
Examples
For the implementation of changeset/1
, see Elixir.PhoenixApiToolkit.Ecto.Validators
.
iex> changeset(%{first_name: "Peter", last_name: "Pan"}) |> validate_ilike_safe([:first_name, :last_name])
#Ecto.Changeset<action: nil, changes: %{first_name: "Peter", last_name: "Pan"}, errors: [], data: %{}, valid?: true>
iex> changeset(%{first_name: "Peter%"}) |> validate_ilike_safe(:first_name)
#Ecto.Changeset<action: nil, changes: %{first_name: "Peter%"}, errors: [first_name: {"may not contain _ % or \\", [validation: :format]}], data: %{}, valid?: false>
iex> changeset(%{first_name: "Pet_er"}) |> validate_ilike_safe(:first_name)
#Ecto.Changeset<action: nil, changes: %{first_name: "Pet_er"}, errors: [first_name: {"may not contain _ % or \\", [validation: :format]}], data: %{}, valid?: false>
iex> changeset(%{first_name: "Pet\\er"}) |> validate_ilike_safe(:first_name)
#Ecto.Changeset<action: nil, changes: %{first_name: "Pet\\er"}, errors: [first_name: {"may not contain _ % or \\", [validation: :format]}], data: %{}, valid?: false>
@spec validate_order_by(Ecto.Changeset.t(), Enum.t()) :: Ecto.Changeset.t()
Validate the value of an order_by
query parameter. The format of the parameter
is expected to match ~r/^(asc|desc|asc_nulls_last|desc_nulls_last|asc_nulls_first|desc_nulls_first):(\w+)$/
(may be repeated, comma-separated).
The supported fields should be passed as a list or MapSet
(which performs better) to orderables
.
If the change is valid, the original change is replaced with a keyword list of
{:field, :direction}
, which is supported by PhoenixApiToolkit.Ecto.DynamicFilters.standard_filters/6
.
examples
Examples
For the implementation of changeset/1
, see Elixir.PhoenixApiToolkit.Ecto.Validators
.
@orderables ~w(first_name last_name) |> MapSet.new()
iex> changeset(%{order_by: "asc:last_name"}) |> validate_order_by(@orderables)
#Ecto.Changeset<action: nil, changes: %{order_by: [asc: :last_name]}, errors: [], data: %{}, valid?: true>
iex> changeset(%{order_by: "invalid"}) |> validate_order_by(@orderables)
#Ecto.Changeset<action: nil, changes: %{order_by: []}, errors: [order_by: {"format is asc|desc:field", []}], data: %{}, valid?: false>
iex> changeset(%{order_by: "asc:eye_count"}) |> validate_order_by(@orderables)
#Ecto.Changeset<action: nil, changes: %{order_by: []}, errors: [order_by: {"unknown field eye_count", []}], data: %{}, valid?: false>
iex> changeset(%{order_by: nil}) |> validate_order_by(@orderables)
#Ecto.Changeset<action: nil, changes: %{}, errors: [], data: %{}, valid?: true>
iex> changeset(%{order_by: "asc:last_name,desc_nulls_last:first_name"}) |> validate_order_by(@orderables)
#Ecto.Changeset<action: nil, changes: %{order_by: [asc: :last_name, desc_nulls_last: :first_name]}, errors: [], data: %{}, valid?: true>
@spec validate_plaintext(Ecto.Changeset.t(), atom() | [atom()]) :: Ecto.Changeset.t()
Validates that field
(or multiple fields) contains plaintext.
examples
Examples
For the implementation of changeset/1
, see Elixir.PhoenixApiToolkit.Ecto.Validators
.
iex> changeset(%{first_name: "Peter", last_name: "Pan"}) |> validate_plaintext([:first_name, :last_name])
#Ecto.Changeset<action: nil, changes: %{first_name: "Peter", last_name: "Pan"}, errors: [], data: %{}, valid?: true>
iex> changeset(%{first_name: "Peter{}"}) |> validate_plaintext(:first_name)
#Ecto.Changeset<action: nil, changes: %{first_name: "Peter{}"}, errors: [first_name: {"can only contain a-Z 0-9 _ . , - ! ? and whitespace", [validation: :format]}], data: %{}, valid?: false>
@spec validate_searchable(Ecto.Changeset.t(), atom(), atom(), keyword()) :: Ecto.Changeset.t()
Validate a searchable field. If the value of field
is postfixed with '*',
a fuzzy search instead of a equal_to match is considered to be intended. In this case, the value
must be at least 4 characters long and must be (i)like safe (as per validate_ilike_safe/2
),
and is moved to search_field
. The postfix '*' is stripped from the search string.
The purpose is to pass the changes along to a list
-query which supports searching by
search_field
, and equal_to filtering by field
.
See PhoenixApiToolkit.Ecto.DynamicFilters
for more info on dynamic filtering.
The minimum length for a search string can be overridden with option :min_length
.
examples
Examples
For the implementation of changeset/1
, see Elixir.PhoenixApiToolkit.Ecto.Validators
.
# a last_name value postfixed with '*' is search query
iex> changeset(%{last_name: "Smit*"}) |> validate_searchable(:last_name, :last_name_prefix)
#Ecto.Changeset<action: nil, changes: %{last_name_prefix: "Smit"}, errors: [], data: %{}, valid?: true>
# values without postfix '*' are passed through
iex> changeset(%{last_name: "Smit"}) |> validate_searchable(:last_name, :last_name_prefix)
#Ecto.Changeset<action: nil, changes: %{last_name: "Smit"}, errors: [], data: %{}, valid?: true>
# to prevent too-broad, expensive ilike queries, search parameters must be >=4 characters long
iex> changeset(%{last_name: "Smi*"}) |> validate_searchable(:last_name, :last_name_prefix)
#Ecto.Changeset<action: nil, changes: %{last_name: "Smi"}, errors: [last_name: {"should be at least %{count} character(s)", [count: 4, validation: :length, kind: :min, type: :string]}], data: %{}, valid?: false>
# the min_length value can be overridden
iex> changeset(%{last_name: "Smi*"}) |> validate_searchable(:last_name, :last_name_prefix, min_length: 5)
#Ecto.Changeset<action: nil, changes: %{last_name: "Smi"}, errors: [last_name: {"should be at least %{count} character(s)", [count: 5, validation: :length, kind: :min, type: :string]}], data: %{}, valid?: false>
# additionally, search parameters must be ilike safe, as per validate_ilike_safe/2
iex> changeset(%{last_name: "Sm_it*"}) |> validate_searchable(:last_name, :last_name_prefix)
#Ecto.Changeset<action: nil, changes: %{last_name: "Sm_it"}, errors: [last_name: {"may not contain _ % or \\", [validation: :format]}], data: %{}, valid?: false>
@spec validate_upload(Ecto.Changeset.t(), atom(), binary() | [binary()]) :: Ecto.Changeset.t()
For verifying files uploaded as base64-encoded binaries. Attempts to decode field
and
validate its file signature. The file signature, also known as a file's "magic bytes",
can be looked up on the internet (for example here)
and may be a list of allowed magic byte types.
examples
Examples
For the implementation of changeset/1
, see Elixir.PhoenixApiToolkit.Ecto.Validators
.
@pdf_signature "255044462D" |> Base.decode16!()
@png_signature "89504E470D0A1A0A" |> Base.decode16!()
@png_file "iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAQAAAC1HAwCAAAAC0lEQVR42mNk+A8AAQUBAScY42YAAAAASUVORK5CYII="
@gif_file "R0lGODlhAQABAIAAAP///wAAACH5BAEAAAAALAAAAAABAAEAAAICRAEAOw=="
@txt_file "some text" |> Base.encode64()
# if the signature checks out, the uploaded file is decoded and the changeset valid
iex> cs = changeset(%{file: @png_file}) |> validate_upload(:file, @png_signature)
iex> {cs.valid?, cs.changes.file}
{true, @png_file |> Base.decode64!()}
# multiple signatures can be provided
iex> cs = changeset(%{file: @png_file}) |> validate_upload(:file, [@pdf_signature, @png_signature])
iex> cs.valid?
true
# if the signature does not check out, an error is added to the changeset and the decoded file is discarded
iex> cs = changeset(%{file: @gif_file}) |> validate_upload(:file, [@pdf_signature, @png_signature])
iex> {cs.valid?, cs.errors, cs.changes.file}
{false, [file: {"invalid file type", []}], @gif_file}
# decoding errors are handled gracefully
iex> cs = changeset(%{file: "a"}) |> validate_upload(:file, @pdf_signature)
iex> {cs.valid?, cs.errors}
{false, [file: {"invalid base64 encoding", []}]}
# it is possible to provide a custom validator function (which should return `true` if valid)
iex> cs = changeset(%{file: @txt_file}) |> validate_upload(:file, &String.starts_with?(&1, "some"))
iex> cs.valid?
true
@spec validate_upload(Ecto.Changeset.t(), atom(), atom(), map()) :: Ecto.Changeset.t()
Like validate_upload/3
, but sets the mime type to mime_field
. Parameter
file_sig_mime_map
should be a map of file type signatures to mime types.
examples
Examples
For the implementation of changeset/1
, see Elixir.PhoenixApiToolkit.Ecto.Validators
.
def is_valid_text(binary), do: String.starts_with?(binary, "some")
@signatures %{
("89504E470D0A1A0A" |> Base.decode16!()) => "image/png",
&__MODULE__.is_valid_text/1 => "text/plain"
}
@png_file "iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAQAAAC1HAwCAAAAC0lEQVR42mNk+A8AAQUBAScY42YAAAAASUVORK5CYII="
@gif_file "R0lGODlhAQABAIAAAP///wAAACH5BAEAAAAALAAAAAABAAEAAAICRAEAOw=="
@txt_file "some text" |> Base.encode64()
iex> cs = changeset(%{file: @png_file}) |> validate_upload(:file, :mime_type, @signatures)
iex> {cs.valid?, cs.changes.file, cs.changes.mime_type}
{true, @png_file |> Base.decode64!(), "image/png"}
iex> cs = changeset(%{file: @txt_file}) |> validate_upload(:file, :mime_type, @signatures)
iex> {cs.valid?, cs.changes.file, cs.changes.mime_type}
{true, @txt_file |> Base.decode64!(), "text/plain"}
iex> cs = changeset(%{file: @gif_file}) |> validate_upload(:file, :mime_type, @signatures)
iex> {cs.valid?, cs.errors, cs.changes.file, cs.changes[:mime_type]}
{false, [file: {"invalid file type", []}], @gif_file, nil}