Hey everyone, I have a live view app that is slowly getting bigger and I’m really struggling to find a way to manage all of the logic for each page. Components, queries, page, etc. I was hoping to get some insight on how I can best have file structure and other tips on making sure I can manage all…

I am suggesting a technique I learned from the book Absinthe/GraphQL.. For example… def list_requests_query(criteria \\ []) do query = from(p in Request) Enum.reduce(criteria, query, fn {:limit, limit}, query -> from p in query, limit: ^limit {:offset, offset}, quer…

I think this is the thing I’m looking for when it comes to the querying which will be one step closer to maintaining the chaos I’ve sewn. Thanks y’all!

I usually try to organize my code like this - lib -- project ---- orders ------ order.ex # schema ---- orders.ex # context -- project_web ---- components # for shared/general components ------ header.ex ---- live ------ orders_live -------- orders_live.ex # LV module handle in/out for info where he…

Thanks for responding everyone. The reducer function idea from kokolegorille is exactly what I’m looking for. That will clean up A LOT of my logic.

I’m curious how you name your lib/project_web/live/orders_live/orders_live.ex module, is it one of: ProjectWeb.Live.OrdersLive ProjectWeb.OrdersLive ProjectWeb.Live.OrdersLive.OrdersLive (probably not, but this is the “strict” file name to module name version) I’ve been waffling between them, es…

This blog series by Sasǎ Jurić was really insightful and I’ve adopted some of the practices in my projects

[image] axelson: ProjectWeb.OrdersLive I like it flat, irrespective of being in the live and orders_live folders.

Yes, we usually go with ProjectWeb.OrdersLive, even if that lives in the project_web/live/orders_live directory.

My preference is Web.Live.Orders and web/live/orders.ex (note: not ProjectWeb, just Web; the prefix always felt superfluous and after a bunch of projects without it, I don’t miss it at all).

Maybe I’m a heretic, but I’ve stopped using “Live” in any module (or folder) naming - most things are live now so it seems superfluous. Any non-live UI modules are controllers and/or views and named explicitly. In the example above, I’d go: lib/project_web/orders index.ex - ProjectWeb.Orders.Ind…

I wrote a small utility which is based on this approach and helps me to organize my complex queries. You may like it as well :slightly_smiling_face: [image] Writing dynamic Ecto queries with Composite Learn how to write dynamic Ecto queries efficiently with Composite, optimizing code org…

How to structure a large live view app?

Questions & Help Questions

kokolegorille August 6, 2024, 10:37pm 31

Yes it is not so easy… but I could get some insight from this non-free course