fix(types): overrideTypes work on invalid embeded relation

[avallete]

• When a relation doesn't exist, or that type inference fail to resolve it the new type should be the source of truth for the result. In such case, we don't "merge" the properties together, but just replace the error with the user provided type.
• When chaining the override with .maybeSingle preserve the optionality of the result
• Allow merging between literal object and non literal one eg:

// Given some property like { someProperty: Record<string, Json | null> } // calling overrideType<{ someProperty: { literalProperty: string } }>() // result in: { [key: string]: Json | null someProperty: { literalProperty: string } } 

[github-actions]

🎉 This PR is included in version 1.19.2 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)

Your semantic-release bot 📦🚀

[jdgamble555]

@avallete - Why not have this work with single() as well?

J

[avallete]

@avallete - Why not have this work with single() as well?

J

This should work with single() as well (test is here:

postgrest-js/test/override-types.test-d.ts

Lines 205 to 228 in 1f93ee5

	// Test merging and replacing existing field types in object result
	{
	const result = await postgrest
	.from('users')
	.select()
	.single()
	.overrideTypes<{ username: number }>()
	if (result.error) {
	throw new Error(result.error.message)
	}
	let data: typeof result.data
	expectType<
	TypeEqual<
	typeof data,
	{
	username: number
	data: CustomUserDataType | null
	age_range: unknown
	catchphrase: unknown
	status: 'ONLINE' | 'OFFLINE' | null
	}
	>
	>(true)
	}

)

Difference here is that maybeSingle should always result in an optional (object | null) while single() should give a non null result.