Disable "sparse" from CLI optimize

[zuggamasta]

Hello there,

I have been using gltf-transform mostly from the gltf.report website and I am now moving to the CLI to speedup my tasks.

I render my glbs with cables.gl which can not read the files that went trough the "sparse" process. Disabling sparse seems not to be possible, as it is not exposed?

zuggamasta@M1 cables_experiments % gltf-transform optimize input.glb output.glb --sparse false                                      

error: The following error occured:
       - Unknown option --sparse. 
       
       Synopsis: gltf-transform optimize <input> <output> [OPTIONS...]

I understand that this might be a design decision. If it's not possible to disable that process: How is the process of chaining single commands? I can't seem to get the gist how this would be applied.

I would like to do something like:
gltf-transform join palette input.glb output.glb

But I will get:

error: The following error occured:
       - Too many argument(s) for command join. Got 3, expected exactly 2.
       
       Synopsis: gltf-transform join <input> <output> [OPTIONS...]

Best and thank you in advance

[donmccurdy]

Hi @zuggamasta! The optimize command is meant as a convenient preset pipeline, but its configurability is limited. Other processing steps, options, or reordering of the existing steps, can all be useful at times. For the most control you could write a script using any transforms and options similar to this:

glTF-Transform/packages/cli/src/cli.ts

Lines 380 to 385 in b266c82

	// Baseline transforms.
	const transforms: Transform[] = [dedup()];
	if (opts.instance) transforms.push(instance({ min: opts.instanceMin }));
	if (opts.palette) {

await document.transform(...transforms);

That said, there's no particular reason that --sparse wasn't exposed, and I think that's easy enough to include. :)

I've opened a PR with the change:

• feat(cli): Add --sparse flag in optimize command #1735

[donmccurdy]

And about chaining CLI commands, not currently possible but a longstanding goal, see:

• Support chaining commands on CLI #13
• Accepting standard input and output with CLI #1172

In the meantime the closest thing for easier CLI usage would be to create a custom config with the commands you need, see https://gltf-transform.dev/cli-configuration.