Scope the extensions configuration such as `extensions.<name>.<option>`

Open
#12,894 1 comment 1 reaction 1 assignee View on GitHub

@cscheid is already working on this.

Since Jun 10, 2025.

Assessment

This issue has not been assessed yet.

Description

enhancement extensions

From @cscheid

I've been wondering what the correct design would be for extensions to declare a schema that controls their configuration. I would like Quarto to validate those entries just the same way as we validate our own YAML.
In order to do that, we would have to find a good "root key" for extension configuration in our schema.
What do you think about extensions as that key?

---
title: ...
extensions:
  iconify:
    set: ...
---

From myself:

What can go under extensions could be a new type for contributes in addition to formats, shortcodes, filters, projects, etc. There could be a settings entry which could contain the schema.
I think something similar was discussed in a GitHub discussion

Dominant language
JavaScript
Stars
6k
Forks
458
Avg merge
1d 9h
Merged PRs (30d)
41

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from quarto-dev/quarto-cli

All issues in quarto-dev/quarto-cli

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.