-
Notifications
You must be signed in to change notification settings - Fork 4
Support Absinthe nested changeset validation errors #8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
thetamind
wants to merge
10
commits into
blunt-elixir:reorg
Choose a base branch
from
thetamind:absinthe-nested-errors
base: reorg
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
c0b8b63
absinthe: handle embedded field validation errors
thetamind 68188cb
read address after mutation
thetamind c013c6a
test derive mutation input for embedded field
thetamind 1407660
apparently same error message when using input object
thetamind 20885e4
test: fix GetPerson binding
thetamind 27612a0
join multiple errors on a field with ', '
thetamind 3d408d3
absinthe: handle deeply nested validation errors
thetamind 53e7034
absinthe: errors include path to field
thetamind c044172
fixup! absinthe: handle deeply nested validation errors
thetamind ea17ec6
absinthe: wrap validation errors in input key if input_object
thetamind File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,14 @@ | ||
| defmodule Blunt.Absinthe.Test.Address do | ||
| use Blunt.ValueObject | ||
| import Ecto.Changeset | ||
|
|
||
| field :line1, :string, required: true | ||
| field :line2, :string | ||
|
|
||
| @impl true | ||
| def handle_validate(changeset, _opts) do | ||
| changeset | ||
| |> validate_length(:line1, min: 3) | ||
| |> validate_format(:line1, ~r/(\d)+.*/, message: "should start with a number") | ||
| end | ||
| end |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should the message include a fully qualified key path including the top level input object?
Or should the message only mention the last field (
line1) and thepathkey include a full path?Blunt.Absinthe.Field.dispatch_and_resolvemaybe unwraps:inputfromargsandAbsintheErrorsdoesn't have that knowledge if it should prefix the error key path with:input.Just to compare, the error from Absinthe for a
nilvalue resulting in a type mismatch is this: