How to modularise ent? #2992
ramonmedeiros
started this conversation in
General
Replies: 1 comment
-
Hey @ramonmedeiros, I hope you don't mind, but I converted #2991 to this discussion.
Can you elaborate on this? Do all entities reside on the same database/schema? What do you mean by separated migrations? Do you use versioned or declarative migrations? Note that Ent changes only the ent/schemas that were changed. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi guys,
The codebase that I work with ent is growing and I would like to modularise a little bit, with the goal to separated some entities in modules, so I can do separated migrations and in case some of them change, does not affect other entities.
So, let's say I have 3 or 4 ent modules in my codebase. How these cases work:
Let's say entity A(module 1) has an edge with entity B (module2). Is it possible to keep them connected? use hooks and stuff?
Will my app have one ent client or multiple?
These are the cases that come to my mind, feel free to bring more cases
Beta Was this translation helpful? Give feedback.
All reactions