Typegen - Account for program types automatically

[danielbate]

Currently the default behaviour of the typegen CLI is to generate types for the contract program type:

fuels-ts/packages/abi-typegen/src/cli.ts

Lines 16 to 34 in 49c103b

	export function resolveProgramType(params: {
	contract: boolean;
	script: boolean;
	predicate: boolean;
	}) {
	const { contract, script, predicate } = params;
	const noneSpecified = !contract && !script && !predicate;
	if (contract || noneSpecified) {
	return ProgramTypeEnum.CONTRACT;
	}
	if (predicate) {
	return ProgramTypeEnum.PREDICATE;
	}
	return ProgramTypeEnum.SCRIPT;
	}

We have had a couple of questions on the forum suggesting that they would expect typegen default behaviour to account for predicates:

• https://forum.fuel.network/t/how-to-build-predicate-ad-create-abi-for-predicate/2467/4
• https://forum.fuel.network/t/cant-create-predicate-instance-following-use-type-tutorial-in-ts-sdk/2490/6

So should we adjust typegen to account for all program types? Program type can be inferred from the ABI programType property. The parameters could remain and act as a filter for when a single program type is required.

[arboleya]

[TL;DR] Currently, ABIs have no information about the program type.

---

We touched on this here:

• feat: add Predicate ABIs support to Typegen #750 (comment)

And also here:

• Remove the module kind declaration (i.e. script;, contract;, etc) from Sway files in favour of a forc manifest field sway#4244 (comment)

---

Maybe we should have an explicit issue for this on the Sway repo?

[arboleya]

@nedsalk Should we address this together with the new abi spec PR?

• chore!: support new ABI format #2747

[nedsalk]

@arboleya we can, but I'd do it in a separate PR that can be based off of the "new ABI format" one. Also, I believe that this can bring about some breaking changes like removing contracts/scripts/predicates from the fuels cli if we increase the scope to cover the cli.

[arboleya]

Makes sense, better to do it in isolation.

[petertonysmith94]

This is being implemented in TS-600

[danielbate]

Resolved by #3032