Simulated run option

[pml-lang]

Simulated run option

[pml-lang]

I propose a "simulated run" option that will show the results of a command without truly executing it.

Excellent idea!

--simulate

As far as I know, the argument dryrun is often used for this kind of execution. So maybe we can adhere to that convention. Although IMO simulate is a better term for non-technical people.

show the intended changes to the generated output

I suppose that "intended changes" relates to changes in the file system (directory/file created/copied, etc), and not to changes in the resulting HTML document, right?

An alternatve implementation might be like Terraform's --auto-approve option, wherewith the intended changes are revealed, and the executable by default pauses for user input

That would be more sophisticated, but also a bit more time-consuming to implement. I suggest to start with a simulate/dryrun option, and add more options later, if asked by the community.

also helpfully reveal the locations of the output_directory, resources_directory, etc.

Yes!

dynamically show certain "default values" as resolved relative to your file system

Very helpful too.

Thanks!

[coemgenuslcp]

I hold no personal preference either way of the name choice. I like "simulate" for its clarity, but also "dry run" is a common term, and one that is really not obscure or confusing.

I suppose that "intended changes" relates to changes in the file system (directory/file created/copied, etc), and not to changes in the resulting HTML document, right?

Indeed, showing the files that will be generated or replaced is likely sufficient for the near future. Content changes would obviously be more intricate to implement, and so a topic not worth treating immediately.

[pml-lang]

Content changes would obviously be more intricate to implement, and so a topic not worth treating immediately.

True