Dan Caddigan

Good call out. Your version will work with your particular `cliGeneratePath`, but would break for others. To make this work with any `CLI_GENERATE_PATH`, we'll need to do something similar to...

Interesting... can you give me a more concrete example? Field Resolvers typically reach into an association. For instance, the `User` model would have a `FieldResolver` for `posts`, that would load...

@dzhelezov I think this was happening because I was loading the metadata class here: https://github.com/goldcaddy77/warthog/blob/main/src/decorators/WarthogField.ts In 3.0 I've changed the metadata pipeline to instead write the metadata properties onto the...

Can you give me a quick example of how I'd test this?

@deweyjose - you're right it seems to relate to that issue. Can you turn on TypeORM logging and see what postgres says exactly?

@Suyashtnt since the Warthog CLI proxies to TypeORM, could you use their workaround to get things working in Warthog? This means using the raw commands from this file: https://github.com/goldcaddy77/warthog/blob/main/src/cli/extensions/db-extension.ts

Just started reviewing :)

Change this line: ```typescript import { BaseModel, JSONField, Model, StringField } from 'warthog'; ``` ...to be... ```typescript import { BaseModel, JSONField, JsonObject, Model, StringField } from 'warthog'; ```

Interesting idea. A few questions: - Which pieces of Nest.js do you want that warthog doesn’t provide? - What specific parts of Warthog would you be using? Ultimately we’d need...

Hey all, note that I'm planning on adopting a monorepo in V3!