rgraff
Ash Core Team
I have a validation based on use Ash.Resource.Validation that when invalid returns
{:error,
InvalidAttribute.exception(
field: :variant_key,
path: [:feature_override],
message: "feature variant not found"
)}
The graphql response is missing the path
%{"data" => %{"addFeatureOverrideToAccount" => %{"errors" => [%{"code" => "invalid_attribute", "fields" => ["variant_key"], "message" => "feature variant not found"}], "result" => nil}}}
I expect the path to be ["feature_override","variant_key"]
I’m seeing the same issue in liveview with the error not getting rendered in forms.
Trending in Questions
Hello everyone!
I am new to coding with Elixir/Erlang. And i am looking for some utilities for fuzzing testing like AFL++.
Does anyone ...
New
I’m very new to Elixir, so sorry if this is a silly question:
I am wondering what happens to the mailbox of a process when the machine i...
New
How do I tell Hologram not to escape HTML when substituting into templates?
{Textile.render(@product.long_description)}
escapes the HTM...
New
Background
When trying to execute mix release on a Windows 11 machine for a Phoenix project I get the following error:
* assembling mark...
New
I load tested a plain Phoenix chat app backed by Postgres with 100 million messages in it, everything on default settings, to see what br...
New
I’d like to create a file with 600 permissions (rw-------), but there’s a race condition if I create it and then change the permissions. ...
New
Is there a way to import record definitions in the iex shell for pretty printing (similar to the rr command in the erl shell)? This woul...
New
Other Trending Topics
Edit: 2026 May 15 - This post is archived.
Mob is alive!!
Main docs: mob v0.7.11 — Documentation
A bit of explanation for the slightly c...
New
I fully migrated to my own harness from Anthropic/Gemini and I think it’s time to share it. Welcome DSH, the DeepSeek Harness, fully writ...
New
(I just needed to vent somewhere and LinkedIn is full of hope, or hype, I’m not sure which exactly)
AI dream has many faces, but general...
New
Localize is the next generation localisation library for Elixir. Think of it as ex_cldr version 3.0. The first version will be released ...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
ExRatatui lets you cook up rich terminal UIs in Elixir, powered by Rust’s ratatui via Rustler NIFs. Build interactive terminal applicatio...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #code-sync
- #discussion
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #ai
- #elixirconf-us
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #blog-post
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #security
- #elixirconf-eu
- #processes
- #api
- #forms
- #hex










Showing Posts 1 to 10- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
zachdaniel
Can you try this:
We should make the
pathkey work for all exceptions by default I think, as that is a pretty natural way to set it.rgraff
The path is being set correctly.
Using
Ash.Error.set_path(...)adds to the path but it’s still not in the graphql fields.Yesterday when I was digging I thought I remember seeing builtin errors from constraints also have keys
attribute:andresource:but now I can’t recreate those.rgraff
May be relevant: The argument (feature_override) is an embedded resource that has an attribute (variant_key). The update action being called is on the parent. The action appends the argument into a list of embedded resources (feature_overrides). The validation is on the parent resource because attributes of the parent affect the validation of the embedded children.
zachdaniel
path: ...option work for ash exceptions by default, but it makes sense to do and would be easy.rgraff
The issue isn’t specific to graphql. I have similar issues in Ash Phoenix Forms. The error gets added to the changeset with the path, but something else must not be set correctly because the path gets dropped by graphql and Ash Phoenix Form too.
I’ll see if I can find a easy way to reproduce.
rgraff
@zachdaniel, I hope this is a better explanation.
Given a action with an argument this is an embedded resource:
And when invalid FeatureVariantExists returns:
And I have a form like this:
When the form is invalid, the error is as expected in
form.source.source.errors[]but is not in the nested form forfeature_overrideWhen getting the error from a graphql mutation (instead of form)
zachdaniel
So, for
ash_phoenixthat is definitely an issue, a reproduction test would be greatly appreciated. I can hunt down what might be going wrong. As forash_graphql, it looks like we actually just don’t have path handling logic set up at all. It should be an addition to the existing logic. Thefieldsis a pointer to multiple fields, not a path to the fields.rgraff
I’ll do a PR for an ash_phoenix test to reproduce this.
For ash_graphql, it’s less of an issue for me right now and I’m not sure what the conventions/specs are for errors. I personally would expect a path with camelCase.
zachdaniel
Yeah, I agree we should add a path to the graphql errors and camelcase them
Neophen
@rgraff did you manage to solve it? As i’m running into an issue where using the AshPhoenix form i’m not getting the error for a path, doing an inspect like so:
the
source.source.errorsdoes contain both errorsbut the actual errors doesn’t contain the
title.enerror:This is a custom ash type based on map. here’s a post with more details: