Using Ash Resources as input types
I've occasionally encountered issues using Ash resources as input types to actions of other resources. The most common patterns I've seen to resolve this are to simply turn the inputs into a map and let
The culprit in some cases seems to be AshGraphql, which errors following this pattern:
Internally, there is not a lot of danger to using the
manage_relationship:uuid%{id: uuid}manage_relationshipThe culprit in some cases seems to be AshGraphql, which errors following this pattern:
Internally, there is not a lot of danger to using the
:mapmanage_relationship
The Elixir backend framework for unparalleled productivity. Declarative tools that let you stop wasting time. Use with Phoenix LiveView or build APIs in minutes for your front-end of choice.
2,193Members
Resources
Was this page helpful?
