This felt wrong to me for a long time, but I’ve come around. It’s fine. Code that gets reused or needs further validation can go in contexts. - ThreadSky

tylerayoung.com • 60 days ago

This felt wrong to me for a long time, but I’ve come around. It’s fine. Code that gets reused or needs further validation can go in contexts.

Reposted from Owen Bickford

Years ago, I heard a hot take on a podcast that stuck with me and I've been taking it more seriously in the past few months. Something along the lines of "just write the query in the controller/LV and move on with your life." IIRC, this was a classic Chris Keathley hot take.

Comments

alexloukissas.com•60 days ago

tbh I never liked contexts - so loosely defined as a concept, no two code bases look the same. Phoenix has not gone far enough into being opinionated IMO.

katafrakt.bsky.social•60 days ago

I tend to agree. Context were like "look, we're better than MVC because we have a place where you put the code that does not fit in MVC". And they became just that - a dumping ground for pretty much anything. And there is very little talk about how to make it more organized.

nuno.site•60 days ago

The problem is what opinion should you have. Half the devs hate opinionated frameworks the other half hates lightweight, hard to please everyone.

I think Contexts are balanced in what they are supposed to be, not forcing you into a specific concept but allowing you to organize your code better.

alexloukissas.com•60 days ago

I like strong opinions and strong guard rails! Innovation comes not from building things in new ways, but building new things that make $$$

nuno.site•60 days ago

In Phoenix you have Ash if you want more structure, personally I think Ash is a too much prescriptive, but to each their own.

Learning Django for instance is way more complicated than Phoenix (if we discard the argument of Functional Language vs Imperative).

nuno.site•60 days ago

I don't disagree with you on that.
I love coding and the craft but I also prefer rules because I know down the road it will byte you in the arse. BUT there is a balance to achieve between expressiveness and complexity.
The more you increase prescription the more the barrier of entry is.

alexloukissas.com•60 days ago

It is like APIs! It’s really hard to define good ones but when you use good ones, things are so easy.

nuno.site•60 days ago

Indeed, that is the thing, I think Elixir is simple enough for you to easily define a set of rules/APIs at the project level. Don't like contexts? Don't use it, pretty easy to do. Prefer a service layer approach? Go with that. Just define it at the start of the project.

moosie.us•60 days ago

1. Write the query you need in the LiveView/Controller.

2. Break out what’s prudent into a base query within a context (like handling tenancy).

3. Pipe that base query into what your view needs.

It’s that shrimple 🦐

Comments

Posting Rules

Reply