Thanks for contribution!

by making it & Entity it means we add all entity properties which is not truth either. Not sure if we should merge it.

by making it & Entity it means we add all entity properties which is not truth either. Not sure if we should merge it.

That's why I define those nullable properties as TypeScript optional types. See the prop address in my example.

With my change, the following is true, because { foo: type } & { foo?: type } still resolves to { foo: type }

@Entity()
export default class User {
    @PrimaryGeneratedColumn('uuid') id: string
    @Column() name: string
    @Column({ nullable: true }) address?: string
    @Column({ nullable: true }) age?: number
}

// ...

const user = { name: 'John Doe', address: 'Somewhere' }
const createdUser = await this.repository.save(user)

createdUser.address // okay
createdUser.age // error, might be undefined

okay, lets merge it, and lets see how people react to this change. Thank you for the contribution!