Setting path on an error

Questions & Help Questions
, ,
3

The path is being set correctly.

      {:error,
       InvalidAttribute.exception(
         field: :variant_key,
         path: [:feature_override],
         message: "feature variant not found"
       )
       |> IO.inspect()}

%Ash.Error.Changes.InvalidAttribute{
  field: :variant_key,
  message: "feature variant not found",
  private_vars: nil,
  value: nil,
  changeset: nil,
  query: nil,
  error_context: [],
  vars: [],
  path: [:feature_override],
  stacktrace: #Stacktrace<>,
  class: :invalid
}

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: and resource: but now I can’t recreate those.