Fabrizio Ruggeri
Fabrizio Ruggeri
it looks like there's no similar way or, at the least, I wasn't able to find one
I see. Definitely harder but doable. Thanks
@Enalmada as a temporary workaround I forked the project and created the package `type-graphql-edge` that runs on edge environment. The option and the logic to emit schema file is removed...
I tried several approach to this and trying to alias the node libraries is too hard to make it reasonable. It only works in very simple setup, but for example...
@akhdefault I'm only going to work on it if this is the direction the maintainer of the library wants to pursuit.
So, let me reply to each point - Use `await import`: I agree, this should not be done - going with subpath: yes, this is the only drawback I see,...
What do you mean? The definition is the only untouched part
Oh, I see what you mean. The current solution in type-graphql is a workaround to actually be sure there's only one instance of typegraphql in node_modules. For example it's the...
This message makes me very happy. I'll also be very happy of helping if there's any need
This is the relevant section ``` model Caption { /// @TypeGraphQL.omit(input: ["create"]) id String @id @default(auto()) @map("_id") @db.ObjectId /// @TypeGraphQL.omit(input: true) createdAt DateTime @default(now()) /// @TypeGraphQL.omit(input: true) updatedAt DateTime @updatedAt...