revati
In classical phoenix app if i would have Accounts context and Users schema, i would call Accounts.create_user, but in Ash context, Having Accounts api and User resource, when defining code_interface on resource, i have to call User.create. I would much rather have Accounts.create_user.
It would be great to be able to do something like:
defmodule MyApp.MyApi do
use Ash.Api
resources do
resource MyApp.MyApi.MyResource
resource MyApp.MyApi.MyAnotherResource
end
code_interface do
define :create_resource, resource: MyApp.MyApi.MyResource, action: :create
define :create_another_resource, resource: MyApp.MyApi.MyAnotherResource, action: :create
end
end
so i wiuld be able to call MyApp.MyApi.create_resource and so on.
Where Next?
Trending in Questions
Other Trending Topics
Latest Ash Threads
Latest on Elixir Forum
Sponsor Spotlight
Error tracking, logs, APM, uptime and cron monitoring in one dev-friendly platform. Find and fix problems before your users notice.
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
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #ai
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Master modern tools, write cleaner code, and tackle real-world challenges.
Bringing learning, work and compliance together since 1987.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 2- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
zachdaniel
You can actually accomplish this today like so:
don’t add
define_for YourApiand then in your api module, call
This will put the functions in the api module. Some users reported compile time/dependency issues doing this in the past, but it’s actually possible that we’ve resolved this with some internal things we’ve done to reduce compilation dependencies. If you have similar issues, you can put the interface in a different module, .e
MyApp.Accounts.Interface, and that should resolve those issues.EDIT: With that said, the idea of having a DSL specifically for it in the api sounds interesting, and is something I’d be willing to explore, providing we can solve for the compilation dependency issues (if they still exist).
revati
Worked like a charm. Just wanted to let you know, there were no conflicts, no errors. 10mins i refactored all my resources to this.