You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First things first, this is an awesome and very useful package 🙌
I have experienced problems with models that have relations to themselves while using the separateRelationFields flag. First, the school_relation class is generated, and afterward the actual school class. This results in school_relation.ts missing imports from school.ts which I need to add manually later. Not a huge deal but it gets tedious on a large-scale project. Maybe this can be solved by reverting the order so that we first generate school.ts and then school_relation.ts?
Expected Behavior
Imports are also generated.
Actual Behavior
Imports are not generated.
Steps to Reproduce the Problem
define a model in schema.prisma
model School {
id String
School School @relation()
}
First things first, this is an awesome and very useful package 🙌
I have experienced problems with models that have relations to themselves while using the
separateRelationFields
flag. First, theschool_relation
class is generated, and afterward the actualschool
class. This results inschool_relation.ts
missing imports fromschool.ts
which I need to add manually later. Not a huge deal but it gets tedious on a large-scale project. Maybe this can be solved by reverting the order so that we first generateschool.ts
and thenschool_relation.ts
?Expected Behavior
Imports are also generated.
Actual Behavior
Imports are not generated.
Steps to Reproduce the Problem
define a model in schema.prisma
define a generator
run
prisma generate
Specifications
The text was updated successfully, but these errors were encountered: