quarto-dev / quarto-dev/quarto-cli

completions for html-pre-tag-processing on fenced div

Open
#10,076 2 comments 0 reactions 1 assignee View on GitHub

@gordonwoodhull is already working on this.

Since Jun 25, 2024.

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

Description

Continuing #10055

Completions for fenced divs were not behaving as I would expect in VSCode (missing results, strange results), so I was unable to test the completion for html-pre-tag-processing.

I don't know if it's important to get autocomplete for this obscure new feature in 1.5 but we can debug/properly configure my VSCode at some point.

I think it would look like this (unless it should go under an existing group):

diff --git a/src/resources/editor/tools/attrs.yml b/src/resources/editor/tools/attrs.yml
index fb03fac2c..40f7f70fb 100644
--- a/src/resources/editor/tools/attrs.yml
+++ b/src/resources/editor/tools/attrs.yml
@@ -320,6 +320,13 @@
     - value: .hidden
       doc: Hide content from view
 
+## html-pre-tag-processing
+- group: html-processing
+  contexts: [div]
+  completions:
+    - value: 'html-pre-tag-processing="parse"'
+      doc: Parse the pre tag in the HTML Raw Block into the Pandoc AST
+
 # revealDiv
 
 - group: revealDiv

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.