ash-project / ash-project/ash

4.0: reverse conditions in the `atomic` callback of 4.0

Open
#1,627 0 comments 1 reaction 0 assignees View on GitHub
enhancement
Dominant language
Elixir
Stars
2.5k
Forks
426
Avg merge
23h 26m
Merged PRs (30d)
46

Description

Right now, you say the condition whereby the error should be raised. In 4.0, this condition should be flipped to be the condition where by the error should *not* be raised. This will mirror the upcoming support of `validate expr(thing_that_must_be_true)`.

Contributor guide

Open the contributing guide

Research direction

Start by locating the `atomic` callback implementation and the existing or upcoming `validate expr` support referenced in the issue. Confirm how the callback currently interprets its condition, then verify that the 4.0 behavior mirrors the stated `validate expr(thing_that_must_be_true)` semantics.

Written by the indexing model from the issue text.

Assessment

Tech stack
elixir
Domain
backend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.