kioopi
When i have a Domain with a Resource, lets say Flora and Plant, i can add to the code interface of the Domain in a fragment by re-opening the resources block.
Like this:
resources do
resource App.Flora.Plant do
define :grow
end
end
But calling Ash.Domain.Info.resources(App.Flora) now returns the resource twice.
[App.Flora.Plant, App.Flora.Plant]
Is there a way to make that work without this change up the output of the inspection tools?
Where Next?
Trending in Questions
Other Trending Topics
Latest Ash Threads
Latest on Elixir Forum
Sponsor Spotlight
Elixir, Erlang & messaging conferences from Code Sync. Next up: ElixirConf US (10–11 Sep) & Code BEAM Europe (21–22 Oct), Haarlem + online.
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
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #hex
- #security
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!
Practical resources that improve the lives of professional developers.
Master modern tools, write cleaner code, and tackle real-world challenges.
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 8- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
zachdaniel
We can fix this, but is there a particular reason that you need to reopen the resource section?
kioopi
I have a directory/namespace that contains as much of the code for a feature as possible. A supervisor, actions, etc, and I want to add the new actions to the domain’s code interface.
If here is a better way than adding the different files from my feature dir in the corresponding files in the “core” app i’d be happy to hear about it.
zachdaniel
I think I might need to see more code samples, I’m not quite following
kioopi
Sorry if i’m not clear enough. Pushed the code to github
Domain: XO/lib/xo/games.ex at main · kioopi/XO · GitHub
Resource: XO/lib/xo/games/game.ex at main · kioopi/XO · GitHub
The directory lib/xo/games/commentator/ contains code to add a LLM backed commentator for the game:
Fragment for Resource: XO/lib/xo/games/commentator/game_fragment.ex at main · kioopi/XO · GitHub
Fragment for Domain: XO/lib/xo/games/commentator/domain_fragment.ex at main · kioopi/XO · GitHub
zachdaniel
Ah, sorry I totally misunderstood the fragment bit. That does seem like a problem. It’s not necessarily a bug but we can fix it by combining any duplicate resource declarations at compile time. Please open an issue!
kioopi
Will do. Is that an Ash issue or rather for Spark?
zachdaniel
An
ashissue.kioopi
https://github.com/ash-project/ash/issues/2683