A command that lists all available native (no subsystem options) project options?

[wlatendresse]

Description

Is it possible to generate, with a single command (from the command line) or a short sequence of commands, if absolutely necessary, one or more (depending on Quarto's internal structure) files (stdout is perfect as well) that represent the complete hierarchy tree of possible configuration options processed by Quarto?

Why I think the existence of such a feature or command is important and is an essential basic feature:

1. Such a command would enable a quarto user, without knowing all of Quarto’s internals, to programmatically generate test documents that could be used to check Quarto for correct or incorrect behavior. (This is my actual motivation for this question, because I am still dissatisfied with the overall quality in some areas (or rather with the fact that some errors have not been noticed long ago) and think this issue could be resolved with a little more automated testing. However, such tests would require, among other things, knowledge of all possible configuration options for a project. Gathering this information from the documentation seems unnecessarily time-consuming, tedious and error-prone from a programmer’s perspective.)

2. Such a command would represent a great way for any new user to instantly get an exhaustive overview of all the available options without having to spend days or weeks plowing through the documentation. With appropriately meaningful option names, such a command would enable an intuitive and exploratory approach. (And we all know, thanks to numerous theories (Self-Determination Theory - SDT, Flow Theory, Hedonic Reinforcement, etc.), that people prefer to spend more time on things that are more fun to them.)

3. The least important reason: As a bonus, the resulting file might even include links to the documentation that explains every single option in broad details.

[mcanouil]

• Documentation for all YAML options #6585
• https://quarto.org/docs/reference/

[wlatendresse]

No, that’s not at all the same thing, because in the reference, you need a finite number of clicks just to wade through it. Plus, it’s not a ready-made configuration file that invites experimentation.

But I’m withdrawing the question anyway, because apparently such a configuration file can be generated relatively easily using DeepWiki and a corresponding question.

I haven’t yet checked whether Quarto can actually process this file without any issues, but it at least represents a clear starting point.

For interested researchers, here is the relevant question:

Can you generate a valid YAML file with ALL possible project options, that quarto can process,
including a brief description and a documentation URL of this specific option
that contains the further description as a comment?

[wlatendresse]

Of course, this method does not work reliably, as "AI" models (LOL! Our predicted future!) are too stupid to sift through documents and deliver one hundred percent results.

Even for simple tasks that require no intelligence at all and that any typist would easily do with the same instructions.

[wlatendresse]

The schema files, which both describe the YAML option hierarchy and are also used as the basis for generating the reference documentation , are available at GitHub reference sources.

And yet it is not possible to generate a complete text file of all options including a description?

The current architecture leaves a lot to be desired.

[cscheid]

We've repeatedly asked you to abide by our code of conduct and be constructive, and you repeatedly failed to do so. As a result, I am now blocking you from participating here.