Пример
ecto 3.14.1: Validate a plain map with Ecto.Changeset alone: an embedded_schema, no Repo, no database and no ecto_sql
Проверенный пример — hex ecto 3.14.1: Validate a plain map with Ecto.Changeset alone: an embedded_schema, no Repo, no database and no ecto_sql. Контракт…
sha256:ec1c423e61b01693526ccce5e694e6c68ed968878f00b8331b3d82c953abea87
Эта сеть предлагает одно: образец, который собирается. Она запустила его в песочнице и сохранила подписанную квитанцию. Она ничего не оценивает и ничего не гарантирует — собирается ли тот же код у вас, она не измеряла.
Сколько различных ключей подписи подали пройденную квитанцию контракта. Один — только автор; больше одного — значит, кто-то ещё тоже собрал. Ключ создаётся сам и не имеет зарегистрированной личности, поэтому считаются ключи, а не люди.
MIT-0
Свидетельства выполнения
Заявленное окружение и подписанные запуски разделены, чтобы вы точно видели, что этот образец запускал и где.
- Основа свидетельства
- Подписанный контракт пройден
- Квитанции проверки
- 2
- Ключи подписи, собравшие его
- 2
Заявленная среда
elixir 1 linux x64 elixir 1 elixir mix
Среды запусков проверки
| Окружение | Контракт | Этапы | Запуск |
|---|---|---|---|
| elixir 1 · linux alpine/x64 · docker ed25519:a2ec939a4c60e243 | PASS | compile:PASS · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · hex@1 |
2026-08-14 |
| elixir 1 · linux alpine/x64 · docker ed25519:d91480838ac982c9 | PASS | compile:PASS · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · hex@1 |
2026-08-18 |
Кейс
HOW- Цель
- Validate a plain map with Ecto.Changeset alone: an embedded_schema, no Repo, no database and no ecto_sql
- Пакеты
- Символы
-
- Ecto.Schema.embedded_schema
- Ecto.Changeset.cast
- Ecto.Changeset.validate_required
- Ecto.Changeset.validate_number
- Ecto.Changeset.validate_format
- Ecto.Changeset.validate_length
- Ecto.Changeset.empty_values
- Ecto.Changeset.field_missing?
- Ecto.Changeset.apply_action
- Ecto.Changeset.apply_changes
- Ecto.Changeset.traverse_errors
- Ecto.Changeset.put_change
- Ecto.Changeset.force_change
- Ecto.InvalidChangesetError
- Окружение
- elixir 1
- Создан
- 2026-08-14T14:09:57Z
Контракт
- assert Ecto.Changeset validates with :ecto alone: ecto_sql is not installed and Ecto.Adapters.SQL will not load, while the embedded_schema reports no source table and no prefix where an otherwise identical schema/2 block reports its table name
- assert embedded_schema's own default primary key is an autogenerated binary_id that nothing outside a Repo insert ever fills in, so it stays nil, which is why the schema turns it off
- assert cast/4 keeps only the permitted fields and silently drops the rest, adding no error for a real-but-unpermitted field or for a key that is not a field at all, while changeset.params still holds the raw attempt and permitting that same field would have accepted it with no error either
- assert permitting a field the schema does not have raises ArgumentError, so a typo in the permitted list fails loudly while an unexpected param never does
- assert cast substitutes the field's default for an empty or whitespace-only string, so validate_required reports can't be blank, and that the substituted value is the declared default rather than nil, which silently resets a field that has one
- assert a value that survives the emptiness check is stored untrimmed, so only the check trims
- assert validate_required runs no blank check of its own and reuses changeset.empty_values, so casting with empty_values: [] lets an empty string pass validation while a validator that inspects the value still catches it
- assert passing a function in :empty_values now raises ArgumentError and the two-arity :trim_values option is the replacement
- assert validate_required decides presence with get_field, so a field carrying a non-nil schema default can never be reported missing, on a failing changeset or a passing one
- assert a type failure from cast is reported as is invalid with validation: :cast, leaves the field out of changes, and suppresses the later validators for that field
- assert apply_action/2 returns {:ok, struct} or {:error, changeset} with :action stamped onto the error changeset, apply_action!/2 raises Ecto.InvalidChangesetError, and apply_changes/1 returns the struct even when the changeset is invalid
- assert validate_number stores a %{number} placeholder plus interpolation metadata while validate_format's message is already complete, so a raw error message is not displayable
- assert traverse_errors interpolates and groups the repeated keys of changeset.errors into the field-to-list-of-messages map an API error body is built from, where a plain keyword lookup on changeset.errors returns only the most recent of a field's several errors
- assert put_change writes to changes regardless of the permitted list and regardless of the validators that already ran, is a no-op when the value equals the one on the data, and force_change/3 is the override
Файлы
- csx.json
- lib/csx_ecto/signup.ex
- mix.exs
- mix.lock
- test/contract_test.exs
- test/test_helper.exs