panache-cli 3.5.0__tar.gz → 3.6.0__tar.gz

{panache_cli-3.5.0 → panache_cli-3.6.0}/Cargo.lock

@@ -1203,7 +1203,7 @@ checksum = "1a80800c0488c3a21695ea981a54918fbb37abf04f4d0720c453632255e2ff0e"
 
 [[package]]
 name = "panache"
-version = "3.5.0"
+version = "3.6.0"
 dependencies = [
  "annotate-snippets",
  "assert_cmd",
@@ -1248,7 +1248,7 @@ dependencies = [
 
 [[package]]
 name = "panache-formatter"
-version = "0.21.1"
+version = "0.21.2"
 dependencies = [
  "insta",
  "log",
@@ -1266,7 +1266,7 @@ dependencies = [
 
 [[package]]
 name = "panache-parser"
-version = "0.27.0"
+version = "0.27.1"
 dependencies = [
  "entities",
  "insta",
@@ -1495,18 +1495,18 @@ dependencies = [
 
 [[package]]
 name = "ref-cast"
-version = "1.0.26"
+version = "1.0.27"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "216e8f773d7923bcba9ceb86a86c93cabb3903a11872fc3f138c49630e50b96d"
+checksum = "7e440fb4e4b4147295338efb76001ab9e4efc0e5839df2c47fc5ac2381d365c3"
 dependencies = [
  "ref-cast-impl",
 ]
 
 [[package]]
 name = "ref-cast-impl"
-version = "1.0.26"
+version = "1.0.27"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "2c9283685feec7d69af75fb0e858d5e7378f33fe4fc699383b2916ab9273e03c"
+checksum = "92ecd8964f8453721699a1ed72037b0db49ce2f5a5138486ee89bed6f67cdf3a"
 dependencies = [
  "proc-macro2",
  "quote",
@@ -2345,9 +2345,9 @@ dependencies = [
 
 [[package]]
 name = "zerovec"
-version = "0.11.7"
+version = "0.11.8"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "94b5c6b5976d66c1d703c4fd17d3f5e43c8cedaacf604961b171adc7130896d8"
+checksum = "bb0464e17806c1d976d5cba29399c7f08e516e279e2ba493f63123b5fca67dd8"
 dependencies = [
  "yoke",
  "zerofrom",
@@ -2356,9 +2356,9 @@ dependencies = [
 
 [[package]]
 name = "zerovec-derive"
-version = "0.11.4"
+version = "0.11.5"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "47402523226a02bfe5230160dc3ccc089aa6f6f19e7fcbb4e6f824bbb1b4aa62"
+checksum = "9f212a141d820099d57ffafb9569be9617a6f27d3dc881fbee8fb56642f917a9"
 dependencies = [
  "proc-macro2",
  "quote",

{panache_cli-3.5.0 → panache_cli-3.6.0}/Cargo.toml

@@ -10,7 +10,7 @@ authors = ["Johan Larsson <johan@jolars.co>"]
 
 [package]
 name = "panache"
-version = "3.5.0"
+version = "3.6.0"
 edition.workspace = true
 rust-version.workspace = true
 # `distill_quarto_schema` is a dev-only vendoring bin (src/bin/); keep bare
@@ -52,8 +52,8 @@ path = "src/main.rs"
 required-features = ["cli"]
 
 [dependencies]
-panache-formatter = { path = "crates/panache-formatter", version = "0.21.1" }
-panache-parser = { path = "crates/panache-parser", version = "0.27.0", features = [
+panache-formatter = { path = "crates/panache-formatter", version = "0.21.2" }
+panache-parser = { path = "crates/panache-parser", version = "0.27.1", features = [
     "serde",
     "schema",
 ] }

{panache_cli-3.5.0 → panache_cli-3.6.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: panache-cli
-Version: 3.5.0
+Version: 3.6.0
 Classifier: Development Status :: 5 - Production/Stable
 Classifier: Environment :: Console
 Classifier: Intended Audience :: Developers
@@ -39,9 +39,9 @@ version](https://badge.fury.io/py/panache-cli.svg?icon=si%3Apython)](https://bad
 version](https://badge.fury.io/js/@panache-cli%2Fpanache.svg?icon=si%3Anpm)](https://badge.fury.io/js/@panache-cli%2Fpanache)
 [![codecov](https://codecov.io/gh/jolars/panache/graph/badge.svg?token=uaBVOBfILv)](https://codecov.io/gh/jolars/panache)
 
-A language server, formatter, and linter for Markdown, Quarto, and R Markdown,
-built in Rust with a lossless CST parser and support for external formatters and
-linters on code blocks.
+Panache is a language server, formatter, and linter for Markdown, Quarto, and R
+Markdown, built in Rust with a lossless CST parser and support for external
+formatters and linters on code blocks.
 
 ## Installation
 
@@ -125,11 +125,11 @@ panache format --check document.qmd
 #### External Code Formatters
 
 Panache supports external formatters for code blocks. For example, you can
-configure it to run `air` on R code blocks and `ruff` on Python code blocks:
+configure it to run `arity` on R code blocks and `ruff` on Python code blocks:
 
 ```toml
 [formatters]
-r = "air"
+r = "arity"
 python = "ruff"
 javascript = "prettier"
 typescript = "prettier" # Reuse same formatter
@@ -141,12 +141,12 @@ arguments:
 ```toml
 [formatters]
 python = ["isort", "black"]
-javascript = "foobar"
+javascript = "myformatter"
 
 [formatters.isort]
 args = ["--profile=black"]
 
-[formatters.myformatters]
+[formatters.myformatter]
 cmd = "foobar"
 args = ["--print-width=100"]
 stdin = true
@@ -172,8 +172,7 @@ panache lint **/*.{qmd,md}
 As with formatting, Panache supports external linters for code blocks. These are
 configured in the `[linters]` section of the configuration, but due to the
 complexity of linting, including dealing with auto-fixing, external linters
-cannot be customized and only support presets and at the moment only support R
-via the `jarl` linter:
+cannot be customized and only support presets:
 
 ```toml
 # Enable R linting
@@ -198,7 +197,7 @@ The list of LSP features supported by Panache includes, among others:
 - Document symbols/outline
 - Folding ranges
 - Go to definition for references and footnotes
-- Quaro and Bookdown project awareness
+- Quarto and Bookdown project awareness
 
 ## Configuration
 
@@ -223,10 +222,9 @@ line-ending = "auto"
 # External code formatters (opt-in)
 [formatters]
 python = ["isort", "black"] # Sequential formatting
-r = "air"                   # Built-in preset
+latex = "badness"           # Built-in preset
 javascript = "prettier"     # Reusable definitions
 typescript = "prettier"
-yaml = "yamlfmt"            # Formats both code blocks AND frontmatter
 
 # Customize formatters
 [formatters.prettier]
@@ -234,7 +232,7 @@ prepend-args = ["--print-width=100"]
 
 # External code linters
 [linters]
-r = "jarl"      # Enable R linting
+julia = "fatou" # Enable Julia linting
 python = "ruff"
 ```
 
@@ -274,7 +272,7 @@ Then add Panache to your `.pre-commit-config.yaml`:
 ```yaml
 repos:
   - repo: https://github.com/jolars/panache-pre-commit
-    rev: v2.43.1 # Use the latest version
+    rev: v3.4.0 # Use the latest version
     hooks:
       - id: panache-format # Format files
       - id: panache-lint # Lint and auto-fix issues
@@ -282,10 +280,7 @@ repos:
 
 > **Note:** The hooks live in
 > [`jolars/panache-pre-commit`](https://github.com/jolars/panache-pre-commit), a
-> thin shim repo. This avoids `pre-commit autoupdate` resolving to unrelated
-> sub-package tags from this monorepo (e.g. `panache-code-*`). If you currently
-> point at `https://github.com/jolars/panache`, update the `repo:` URL and run
-> `pre-commit autoupdate`.
+> thin shim repo.
 
 Install the hooks:
 
@@ -329,5 +324,5 @@ page](https://panache.bz/guide/performance).
 The development of Panache has simplified considerably thanks to the extensive
 documentation, well-structured code, and testing infrastructure provided by
 Pandoc. We also owe significant debt to the rust-analyzer project, on which
-Panche is heavily inspired.
+Panache is heavily inspired.
 

{panache_cli-3.5.0 → panache_cli-3.6.0}/README.md

@@ -13,9 +13,9 @@ version](https://badge.fury.io/py/panache-cli.svg?icon=si%3Apython)](https://bad
 version](https://badge.fury.io/js/@panache-cli%2Fpanache.svg?icon=si%3Anpm)](https://badge.fury.io/js/@panache-cli%2Fpanache)
 [![codecov](https://codecov.io/gh/jolars/panache/graph/badge.svg?token=uaBVOBfILv)](https://codecov.io/gh/jolars/panache)
 
-A language server, formatter, and linter for Markdown, Quarto, and R Markdown,
-built in Rust with a lossless CST parser and support for external formatters and
-linters on code blocks.
+Panache is a language server, formatter, and linter for Markdown, Quarto, and R
+Markdown, built in Rust with a lossless CST parser and support for external
+formatters and linters on code blocks.
 
 ## Installation
 
@@ -99,11 +99,11 @@ panache format --check document.qmd
 #### External Code Formatters
 
 Panache supports external formatters for code blocks. For example, you can
-configure it to run `air` on R code blocks and `ruff` on Python code blocks:
+configure it to run `arity` on R code blocks and `ruff` on Python code blocks:
 
 ```toml
 [formatters]
-r = "air"
+r = "arity"
 python = "ruff"
 javascript = "prettier"
 typescript = "prettier" # Reuse same formatter
@@ -115,12 +115,12 @@ arguments:
 ```toml
 [formatters]
 python = ["isort", "black"]
-javascript = "foobar"
+javascript = "myformatter"
 
 [formatters.isort]
 args = ["--profile=black"]
 
-[formatters.myformatters]
+[formatters.myformatter]
 cmd = "foobar"
 args = ["--print-width=100"]
 stdin = true
@@ -146,8 +146,7 @@ panache lint **/*.{qmd,md}
 As with formatting, Panache supports external linters for code blocks. These are
 configured in the `[linters]` section of the configuration, but due to the
 complexity of linting, including dealing with auto-fixing, external linters
-cannot be customized and only support presets and at the moment only support R
-via the `jarl` linter:
+cannot be customized and only support presets:
 
 ```toml
 # Enable R linting
@@ -172,7 +171,7 @@ The list of LSP features supported by Panache includes, among others:
 - Document symbols/outline
 - Folding ranges
 - Go to definition for references and footnotes
-- Quaro and Bookdown project awareness
+- Quarto and Bookdown project awareness
 
 ## Configuration
 
@@ -197,10 +196,9 @@ line-ending = "auto"
 # External code formatters (opt-in)
 [formatters]
 python = ["isort", "black"] # Sequential formatting
-r = "air"                   # Built-in preset
+latex = "badness"           # Built-in preset
 javascript = "prettier"     # Reusable definitions
 typescript = "prettier"
-yaml = "yamlfmt"            # Formats both code blocks AND frontmatter
 
 # Customize formatters
 [formatters.prettier]
@@ -208,7 +206,7 @@ prepend-args = ["--print-width=100"]
 
 # External code linters
 [linters]
-r = "jarl"      # Enable R linting
+julia = "fatou" # Enable Julia linting
 python = "ruff"
 ```
 
@@ -248,7 +246,7 @@ Then add Panache to your `.pre-commit-config.yaml`:
 ```yaml
 repos:
   - repo: https://github.com/jolars/panache-pre-commit
-    rev: v2.43.1 # Use the latest version
+    rev: v3.4.0 # Use the latest version
     hooks:
       - id: panache-format # Format files
       - id: panache-lint # Lint and auto-fix issues
@@ -256,10 +254,7 @@ repos:
 
 > **Note:** The hooks live in
 > [`jolars/panache-pre-commit`](https://github.com/jolars/panache-pre-commit), a
-> thin shim repo. This avoids `pre-commit autoupdate` resolving to unrelated
-> sub-package tags from this monorepo (e.g. `panache-code-*`). If you currently
-> point at `https://github.com/jolars/panache`, update the `repo:` URL and run
-> `pre-commit autoupdate`.
+> thin shim repo.
 
 Install the hooks:
 
@@ -303,4 +298,4 @@ page](https://panache.bz/guide/performance).
 The development of Panache has simplified considerably thanks to the extensive
 documentation, well-structured code, and testing infrastructure provided by
 Pandoc. We also owe significant debt to the rust-analyzer project, on which
-Panche is heavily inspired.
+Panache is heavily inspired.

{panache_cli-3.5.0 → panache_cli-3.6.0}/crates/panache-formatter/CHANGELOG.md

@@ -1,5 +1,13 @@
 # Changelog
 
+## [0.21.2](https://github.com/jolars/panache/compare/panache-formatter-v0.21.1...panache-formatter-v0.21.2) (2026-08-20)
+
+### Bug Fixes
+- **formatter:** preserve R T and F aliases ([`153ea95`](https://github.com/jolars/panache/commit/153ea957138f7be00f3634ec13864da4217fb858))
+
+### Dependencies
+- updated crates/panache-parser to v0.27.1
+
 ## [0.21.1](https://github.com/jolars/panache/compare/panache-formatter-v0.21.0...panache-formatter-v0.21.1) (2026-08-17)
 
 ### Bug Fixes

{panache_cli-3.5.0 → panache_cli-3.6.0}/crates/panache-formatter/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "panache-formatter"
-version = "0.21.1"
+version = "0.21.2"
 edition.workspace = true
 rust-version.workspace = true
 include = [
@@ -19,7 +19,7 @@ keywords = ["quarto", "pandoc", "markdown", "formatter"]
 categories = ["text-processing"]
 
 [dependencies]
-panache-parser = { path = "../panache-parser", version = "0.27.0" }
+panache-parser = { path = "../panache-parser", version = "0.27.1" }
 log = { version = "0.4.31", features = ["release_max_level_debug"] }
 rowan = "0.17.0"
 serde = { version = "1.0.228", features = ["derive"], optional = true }

{panache_cli-3.5.0 → panache_cli-3.6.0}/crates/panache-formatter/src/config.rs

@@ -271,9 +271,6 @@ impl Config {
             dialect: self.dialect(),
             extensions: self.parser_extensions.clone(),
             pandoc_compat: self.parser,
-            // The formatter re-parses only for internal checks (idempotency,
-            // code-block handling) where citation-vs-crossref classification
-            // doesn't affect output, so the built-in prefix set suffices here.
             crossref_prefixes: Vec::new(),
             refdef_labels: None,
         }
@@ -335,10 +332,6 @@ impl ConfigBuilder {
 mod schema_tests {
     use super::*;
 
-    /// Assert the emitted JSON Schema exposes exactly the expected lowercase
-    /// wire values (and no PascalCase variant names). Substring checks keep this
-    /// robust to schemars emitting a flat `enum` array vs. a `oneOf`-of-`const`
-    /// shape — the doc comments on some variants become per-value descriptions.
     fn assert_wire_values<T: schemars::JsonSchema>(expected: &[&str]) {
         let s = serde_json::to_string(&schemars::schema_for!(T)).unwrap();
         for value in expected {

{panache_cli-3.5.0 → panache_cli-3.6.0}/crates/panache-formatter/src/directives.rs

@@ -68,28 +68,22 @@ impl DirectiveKind {
 /// assert_eq!(parse_directive("<!-- regular comment -->"), None);
 /// ```
 pub fn parse_directive(comment_text: &str) -> Option<Directive> {
-    // Strip HTML comment markers
     let content = comment_text.trim();
 
     if !content.starts_with("<!--") || !content.ends_with("-->") {
         return None;
     }
 
-    // Reject comments where the opening `<!--` and closing `-->` markers
-    // overlap or abut (e.g. `<!--->`); the inner slice would otherwise panic.
     if content.len() < 7 {
         return None;
     }
 
-    // Extract content between <!-- and -->
     let inner = content[4..content.len() - 3].trim();
 
-    // Check for panache directive prefix
     if !inner.starts_with("panache-ignore") {
         return None;
     }
 
-    // Parse the directive
     match inner {
         "panache-ignore-start" => Some(Directive::Start(DirectiveKind::IgnoreBoth)),
         "panache-ignore-end" => Some(Directive::End(DirectiveKind::IgnoreBoth)),
@@ -127,14 +121,12 @@ impl DirectiveTracker {
                 true
             }
             Directive::End(kind) => {
-                // Check if the top of the stack matches
                 if let Some(top) = self.stack.last()
                     && top == kind
                 {
                     self.stack.pop();
                     return true;
                 }
-                // Mismatch or end without start
                 false
             }
         }
@@ -178,8 +170,6 @@ impl Default for DirectiveTracker {
 pub fn extract_directive_from_node(node: &SyntaxNode) -> Option<Directive> {
     use crate::syntax::SyntaxKind;
 
-    // HTML comments can be parsed as COMMENT, HTML_BLOCK, or INLINE_HTML
-    // depending on context (block-level vs inline) and dialect.
     if node.kind() != SyntaxKind::COMMENT
         && node.kind() != SyntaxKind::HTML_BLOCK
         && node.kind() != SyntaxKind::HTML_BLOCK_RAW
@@ -273,8 +263,6 @@ mod tests {
 
     #[test]
     fn test_parse_directive_overlapping_markers() {
-        // Comments where the opening `<!--` and closing `-->` markers overlap
-        // (or abut) must not panic when slicing the inner content.
         assert_eq!(parse_directive("<!--->"), None);
         assert_eq!(parse_directive("<!-->"), None);
         assert_eq!(parse_directive("<!---->"), None);
@@ -282,7 +270,6 @@ mod tests {
 
     #[test]
     fn test_parse_directive_future_extension() {
-        // Future syntax for rule-specific ignores should return None for now
         assert_eq!(
             parse_directive("<!-- panache-ignore-lint heading-hierarchy -->"),
             None
@@ -341,11 +328,9 @@ mod tests {
     fn test_tracker_mismatch() {
         let mut tracker = DirectiveTracker::new();
 
-        // End without start
         let result = tracker.process_directive(&Directive::End(DirectiveKind::IgnoreBoth));
         assert!(!result);
 
-        // Mismatched kinds
         tracker.process_directive(&Directive::Start(DirectiveKind::IgnoreFormat));
         let result = tracker.process_directive(&Directive::End(DirectiveKind::IgnoreLint));
         assert!(!result);

panache_cli-3.6.0/crates/panache-formatter/src/formatter/blockquotes.rs

@@ -0,0 +1 @@
+