Complex Input Flattening - Action or Code Interface?
I have a create action that takes an argument (:member, a :map) which I call
I was hoping to "flatten" the API a bit. I know there is a way to use custom_input to transform that when creating a code interface, but the examples in the docs are fairly simple (like going from artist to artist.id). I was able to get it to work this way, so functionality wise it works.
It feels weird to have this flattening logic defined with the code interface, is that the right way? I feel like this should process of going from a few args to a more complex arg should be in the action. I guess I can have a custom change action which calls
change manage_relationshipmanage_relationshipI was hoping to "flatten" the API a bit. I know there is a way to use custom_input to transform that when creating a code interface, but the examples in the docs are fairly simple (like going from artist to artist.id). I was able to get it to work this way, so functionality wise it works.
It feels weird to have this flattening logic defined with the code interface, is that the right way? I feel like this should process of going from a few args to a more complex arg should be in the action. I guess I can have a custom change action which calls
Ash.Changeset.manage_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
Similar Threads
Was this page helpful?
