Slight Refactor for prisma model code.

[Brocktho]

This project is incredibly impressive and useful, but at the same time incredibly overwhelming to step into. Even coming from a fairly extensive remix background and having stayed semi checked into whats going on with the project; I struggled a bit to actually take this template and make something with it. There's a lot of good helpers and started pieces and obviously with a project so large it's gonna be like jumping into the deep end of a pool for any new user. However, I still think there's a reasonable argument to be made about having some stronger opinions on server code placement.

Remix definitely encourages co-location of client and server code, but with how routes are defined and nested in somewhat non-intuitive ways (at least to me) I think it could be useful to move to a model folder or something similar like other remix example stacks have done. Having all (or at least most) prisma calls centralized in one folder or zone could make it a bit easier to track down where specific updates are happening rather than having to figure out every single route individually and see what each one is doing.

There's also some mixed signals about "preferred approach" in some sections where in the __note-editor.tsx file we have a full schema definition with all the constants and individual schemas built up, but for something like the login form we have a separate import zone for things like PasswordSchema and UsernameSchema in the utils folder.

I don't see any decision doc or strong feelings for this sort of idea, so I just wanted to kind of gauge interest in this and see if it's worth some refactor effort. I'd personally be willing and interested in such a change as I feel it can make things a bit easier to follow especially if you come from an MVC background.

[goodeats]

FWIW I think a part of the "mixed signals" is meant to demonstrate different ideas for devs to determine how to go forward with their app -- I think I remember seeing KCD saying that at one point

As someone who has built a handful of apps off the epic-stack, this is actually what I've been doing! I have *.db.server.ts for each model and each set of CRUD actions. Then I have a shared CRUD action server that each model db server is mapped to. My hope is that if I need to make a change, say prisma update or migrate to drizzle, I won't have to update all my routes. Just like you're saying.

I've even taken it a step further and adopted the remix-flat-routes approach since an earlier project with more polymorphic relations was a mess of nested folders in the file explorer. Not sure I've seen anyone do this from the server side so idk how others might feel about doing this :D

(these are all in my app/models directory)

[kentcdodds]

I do have thoughts on this, and I think I'd prefer to share them in a podcast episode rather than a decision document. I think that would make more sense. Would anyone be interested in asking this question on the Call Kent podcast? https://kcd.im/calls