Improve pre/post render script logging

[cderv]

This is an idea coming from work on

• run post-render script only on project render quarto-web#1612

The logging was not completely explicit as it was showing on script name without context.

This PR adds Running script before.

Also it introduces an idea: Set a new env var so that the pre/post render script know when then need to make there option console.log quiet.

If this seems a good idea, I can add test.

Comment on the process

I initially did some commit to add the env var with others

quarto-cli/src/command/render/project.ts

Lines 326 to 331 in d5dc015

	const prePostEnv = {
	"QUARTO_PROJECT_OUTPUT_DIR": projOutputDir,
	...(projectRenderConfig.behavior.renderAll
	? { QUARTO_PROJECT_RENDER_ALL: "1" }
	: {}),
	};

but in fact, it seems better to defined closer to its meaning,

quarto-cli/src/command/render/project.ts

Lines 974 to 977 in d5dc015

	if (progress && !quiet) {
	info(colors.bold(colors.blue(`Running script '${script}'`)));
	env["QUARTO_PROJECT_SCRIPT_PROGRESS"] = "1";
	}

which leads to

• QUARTO_PROJECT_SCRIPT_PROGRESS is set to 1 means progress can be shown
• QUARTO_PROJECT_SCRIPT_PROGRESS is unset, means no progress is expected

[cscheid]

@cderv I'm pushing this to v1.8 but feel free to move back to v1.7 if you've made the changes we talked about last week.

[cderv]

I rebased - this is where I was.

[cscheid]

Right - we had talked about using QUARTO_QUIET and QUARTO_PROGRESS instead, and making that part of the codebase less branchy. I think that would be a worthy change (and doesn't need to happen for 1.7).

[cderv]

QUARTO_QUIET and QUARTO_PROGRESS instead

Yeah I used more verbose env var name because I feel those two are too generic... We are in pre-render post-render script context here, so I wanted to scope the variable name as it is for QUARTO_PROJECT_OUTPUT_DIR

It does not apply to quarto run for example. So it seems there topic here is to make env var available in a clever way, wherever they are supposed to (e.g quarto run, pre-render, post-render, execution ? Lua filters ?)

A border topic.

making that part of the codebase less branchy.

I have done that part by removing the if else and using a default handler.run. Did you have in mind something more generic like making quarto run and pre/post render sharing even more logic ?

Let's continue in 1.8 then.