jjabba
Where should I put my `def changeset` code when using Phoenix 1.4 and Contexts?
I’m working on an App using phoenix 1.4. Im trying to understand in which file to define my Ecto changesets. This is my particular scenario:
Under the ‘Domain’ context im creating entities and actors. These two Ecto schemas are defined in:
lib/myapp/domain/entity.ex & lib/myapp/domain/actor.ex.
My context related business logic lives in lib/my_app/domain/domain.ex.
I read this blog post a while back and to the best of my understanding it suggests to keep schemas clean and free of anything but the schema definitions, and favor putting any changeset definitions in the context (read the ‘Schemas are not models’ section of the blogpost’).
What is the most recent take on this, where should my changeset definitions for entity and actor go?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Build Elixir applications with speed and confidence.
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
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #websockets
- #elixirconf-us
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #performance
- #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.
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.
Enabling companies to succeed by building software people love.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
First 4 of 4 Posts!
Eiji
First of all this article is from
2017and it’s based on release candidate. It’s obviously outdated if you would take a look how to install archive.The best way is to read
phoenixdocumentation:Please make sure to read also related guides.
dimitarvp
Don’t get too hung up on how other people organize their projects. Find a way that looks intuitive to you and your team. The most important metric should be this one:
“How do I organize the project so that if I get a 3 months of vacation I’ll be able to decipher what I did immediately after coming back?”
al2o3cr
FWIW,
phx.gen.schemaincludesimport Ecto.Changesetas part of every generated schema file. I’d consider that a strong endorsement from the framework for puttingchangesetfunctions in schemasjjabba
Thanks!
I’ve eyed through the docs linked by @Eiji, and based on that and the way the
phx.gen.schemabehaves I have decided to put my changeset def in the schema files with@doc false, and use specialized functions in the context as a gateway to access them.