Link variants should be typable with a generic

[lihbr]

Versions

• @prismicio/client: 7.14.0
• node: 22.0.0

Steps to reproduce

1. Create a link field with variants with Slice Machine
2. Check out generated TypeScript

What is expected?

Link variants should be precisely typed when available values are known (always the case for a link field typed after a custom type definition)

This starts by allowing the LinkField type to support another generic to type available variants beyond string but it's not really ideal without reordering generics today (which would be a breaking change).

From here, prismic-ts-codegen could leverage the generic to type variants more precisely the same way it does it for other generic-dependant types (e.g. constrained content relationships)

What is actually happening?

Generated types

{
  navigation: prismic.Repeatable<prismic.LinkField>;
}

Result

Source code

prismic-client/src/types/value/link.ts

Lines 90 to 93 in c45f28d

	export type OptionalLinkProperties = {
	text?: string
	variant?: string
	}

[angeloashmore]

The field value types should primarily be consumed via the generated types rather than handwritten types. Adding another generic seems okay to me. Re-ordering should be avoided, however, as it would break existing generated types.