nyakio
I have a project with multiple resources, each containing resource-specific helper functions. I’m using the Spark formatter to maintain a consistent order for resource sections, but it does not include the helper functions.
In an Ash project, where should these resource-specific helper functions be placed? Should they live in the Domain module, acting like context functions, or would it be better to create separate resource_helper modules? Alternatively, is there a way to configure Spark to place non-standard sections, like helper functions, at the bottom of the resource?
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
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #blog-post
- #phoenix_html
- #iex
- #graphql
- #ai
- #genstage
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #security
- #hex
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Practical resources that improve the lives of professional developers.
Producing high quality Elixir screencasts since 2017.
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!"
First 2 of 2 Posts
barnabasJ
I would differentiate between functions only used internally in the domain and functions that are supposed to be callable from outside the domain.
I would only put functions that are supposed to be called from outside into the domain, so other modules outside this domain only need to use that one module to call functions. If they don’t fit in the normal create/read/update/destroy categories, I would primarily create generic actions on resources and use code_interfaces to create functions for them on the domain.
For functions, I needed in multiple changes/preparations, and so on, I created separate helper modules besides the resources to put them in.
I don’t think the formatted has options for non dsl things at the moment.
nyakio
Aha! Thank you.