RubyGems - apex-ruby - Versions diffs - 1.0.30 → 1.0.32 - Mend

apex-ruby 1.0.30 → 1.0.32

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (490) hide show

data/ext/apex_ext/apex_src/tests/gfm_id_comparison_summary.md DELETED Viewed

@@ -1,96 +0,0 @@
-# GFM Header ID Generation Comparison
-This document summarizes the differences between various
-tools for generating GFM-compliant header IDs.
-## Tools Tested
-- **Pandoc**: General-purpose document converter
-- **Comrak**: Rust-based GFM parser (likely most accurate)
-- **Marked (JavaScript)**: JavaScript markdown parser with
-  gfm-heading-id plugin
-- **Apex**: Our implementation
-## Key Differences
-### 1. Multiple Spaces
-**Comrak/Marked**: Convert to multiple dashes (`multiple---spaces---here`)
-**Pandoc/Apex**: Collapse to single dash (`multiple-spaces-here`)
-### 2. Underscores
-**Comrak/Marked/Pandoc**: Preserve underscores (`heading_with_underscore`)
-- **Apex**: Remove underscores (`headingwithunderscore`)
-### 3. Em/En Dashes
-- **Comrak/Marked/Pandoc**: Convert to double dashes
-  (`em-dash--test`)
-- **Apex**: Remove dashes (`em-dash-test`)
-### 4. Diacritics
-**Comrak/Marked/Pandoc**: Preserve diacritics (`diacritics-émoji-support`)
-- **Apex**: Convert to ASCII (`diacritics-amoji-support`)
-### 5. Non-Latin Characters
-- **Comrak/Marked/Pandoc**: Preserve characters
-  (`cyrillic-привет`)
-- **Apex**: Convert to placeholders (`cyrillic-nn`)
-### 6. Trailing Dashes
-- **Comrak/Marked/Pandoc**: Preserve trailing dashes
-  (`trailing-dash-test-`)
-- **Apex**: Trim trailing dashes (`trailing-dash-test`)
-### 7. Trailing Punctuation
-- **Comrak/Marked/Pandoc**: Preserve trailing punctuation
-  (`special-characters-`)
-**Apex**: Remove trailing punctuation (`special-characters`)
-### 8. Special Characters Only
-- **Comrak**: Generates empty ID for `!@#$%^&*()`
-- **Others**: Generate some ID
-## Recommendations
-Based on the comparison, **Comrak** and **Marked** appear to
-follow GFM rules most closely and produce identical results
-for most cases. To match GFM exactly, we should:
-1. **Preserve underscores** (don't remove them)
-**Convert em/en dashes to double dashes** (not remove them)
-3. **Preserve diacritics** (don't convert to ASCII)
-4. **Preserve non-Latin characters** (don't convert to
-   placeholders)
-5. **Preserve trailing dashes** (don't trim them)
-6. **Preserve trailing punctuation** (don't remove it)
-7. **Handle multiple spaces** - need to verify GFM behavior
-   (Comrak/Marked use multiple dashes)
-## Running the Comparison
-Run the comparison script:
-```bash
-./tests/generate_gfm_ids.sh
-```
-This will show side-by-side comparison of all available
-tools.

data/ext/apex_ext/apex_src/tests/gh_api_test.md DELETED Viewed

@@ -1,6 +0,0 @@
-# Test Header
-## Header with Spaces
-### Heading_with_underscore
-# Em Dash — Test
-## Émoji Support

data/ext/apex_ext/apex_src/tests/ial_demo.html DELETED Viewed

@@ -1,186 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-<head>
-    <meta charset="UTF-8">
-    <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <title>IAL Demo - Attribute Inspector</title>
-    <style>
-        body {
-            font-family: -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, Oxygen, Ubuntu, Cantarell, sans-serif;
-            line-height: 1.6;
-            max-width: 900px;
-            margin: 0 auto;
-            padding: 20px;
-            background-color: #f5f5f5;
-        }
-        .content {
-            background: white;
-            padding: 30px;
-            border-radius: 8px;
-            box-shadow: 0 2px 4px rgba(0,0,0,0.1);
-        }
-        /* Style for elements with attributes - add visual indicator */
-        [class]:hover,
-        [id]:hover {
-            outline: 2px solid #4CAF50;
-            outline-offset: 2px;
-            background-color: rgba(76, 175, 80, 0.1);
-            transition: background-color 0.2s;
-        }
-    </style>
-    <script>
-        // Add tooltips showing all attributes on hover
-        document.addEventListener('DOMContentLoaded', function() {
-            // Create tooltip element
-            const tooltip = document.createElement('div');
-            tooltip.id = 'attribute-tooltip';
-            tooltip.style.cssText = 'position: absolute; background: #333; color: white; padding: 8px 12px; border-radius: 4px; font-size: 12px; font-family: "Courier New", monospace; z-index: 10000; pointer-events: none; opacity: 0; transition: opacity 0.2s; box-shadow: 0 2px 8px rgba(0,0,0,0.3); max-width: 400px; word-wrap: break-word; white-space: normal; line-height: 1.4;';
-            document.body.appendChild(tooltip);
-            // Function to get all attributes as a formatted string
-            function getAttributesString(el) {
-                const attrs = [];
-                if (el.id) attrs.push('id="' + el.id + '"');
-                if (el.className) attrs.push('class="' + el.className + '"');
-                for (let i = 0; i < el.attributes.length; i++) {
-                    const attr = el.attributes[i];
-                    if (attr.name !== 'id' && attr.name !== 'class' && !attr.name.startsWith('data-apex-')) {
-                        attrs.push(attr.name + '="' + attr.value + '"');
-                    }
-                }
-                return attrs.length > 0 ? attrs.join(' ') : 'No attributes';
-            }
-            // Add hover handlers to all elements with attributes
-            const elementsWithAttrs = document.querySelectorAll('[class], [id]');
-            elementsWithAttrs.forEach(el => {
-                // Skip the tooltip itself and elements inside code blocks
-                if (el.id === 'attribute-tooltip' || el.closest('code') || el.closest('pre')) {
-                    return;
-                }
-                el.addEventListener('mouseenter', function(e) {
-                    const attrs = getAttributesString(this);
-                    const tagName = this.tagName.toLowerCase();
-                    tooltip.innerHTML = '<strong>&lt;' + tagName + '</strong> ' +
-                                      (attrs !== 'No attributes' ? attrs : '<em>' + attrs + '</em>') +
-                                      '<strong>&gt;</strong>';
-                    tooltip.style.opacity = '1';
-                    const rect = this.getBoundingClientRect();
-                    let left = rect.left + window.scrollX;
-                    let top = rect.top + window.scrollY - tooltip.offsetHeight - 8;
-                    // Position tooltip
-                    tooltip.style.left = left + 'px';
-                    tooltip.style.top = top + 'px';
-                    // Adjust if tooltip goes off screen
-                    setTimeout(() => {
-                        const tooltipRect = tooltip.getBoundingClientRect();
-                        if (tooltipRect.left < 0) {
-                            tooltip.style.left = '10px';
-                        }
-                        if (tooltipRect.top < 0) {
-                            tooltip.style.top = (rect.bottom + window.scrollY + 8) + 'px';
-                        }
-                        if (tooltipRect.right > window.innerWidth) {
-                            tooltip.style.left = (window.innerWidth - tooltipRect.width - 10) + 'px';
-                        }
-                    }, 0);
-                });
-                el.addEventListener('mouseleave', function() {
-                    tooltip.style.opacity = '0';
-                });
-            });
-            console.log('Attribute inspector loaded. Hover over elements with attributes to see them.');
-        });
-    </script>
-</head>
-<body>
-    <div class="content">
-<h1 id="ial-inline-attribute-lists-demo">IAL (Inline Attribute Lists) Demo</h1>
-<p>This document demonstrates all supported IAL features in Apex.</p>
-<h2 id="block-level-ials-next-line">Block-Level IALs (Next-Line)</h2>
-<p>Block-level IALs appear on a separate line after the element they apply to.</p>
-<h3 id="headings-with-ials">Headings with IALs</h3>
-<h1 id="custom-heading-id">Heading with ID</h1>
-<h2 class="highlight" id="custom-heading-id">Heading with Class</h2>
-<h3 id="heading-id" class="class1 class2">Heading with Both</h3>
-<h4 class="primary large bold" id="heading-with-class">Multiple Classes</h4>
-<h3 id="heading-id">Paragraphs with IALs</h3>
-<p class="tip">This paragraph has a class applied to it.</p>
-<p id="paragraph-id" class="important note">This paragraph has an ID and multiple classes.</p>
-<h3 id="multiple-classes">Lists with IALs</h3>
-<ul class="unordered-list">
-<li>First item</li>
-<li>Second item</li>
-<li>Third item</li>
-<li>Numbered item one</li>
-<li>Numbered item two</li>
-<li>Numbered item three</li>
-</ul>
-<h3 id="paragraphs-with-ials">Blockquotes with IALs</h3>
-<blockquote class="quote inspirational">
-<p>This is a blockquote with attributes.</p>
-</blockquote>
-<h2 id="lists-with-ials">Inline Span-Level IALs</h2>
-<p>Inline IALs appear immediately after inline elements within paragraphs.</p>
-<h3 id="blockquotes-with-ials">Links with Inline IALs</h3>
-<p>This is a <a href="https://example.com">regular link</a> without an IAL.</p>
-<p>Here’s a paragraph with a <a href="https://example.com" class="button">styled link</a> that has a button class.</p>
-<p>You can have <a href="https://example.com" class="link-primary">multiple links</a> with <a href="https://example.com" class="link-secondary">different classes</a> in the same paragraph.</p>
-<p>Links with the <a href="https://example.com">same URL</a> should still work correctly when <a href="https://example.com" class="special-link">one has an IAL</a>.</p>
-<h3 id="inline-span-level-ials">Images with Inline IALs</h3>
-<p><img src="image.png" alt="Regular image" /></p>
-<p><img src="logo.png" alt="Styled image" class="logo centered" /></p>
-<p><img src="icon.png" alt="Image with ID" id="site-icon" class="icon" /></p>
-<h3 id="links-with-inline-ials">Emphasis with Inline IALs</h3>
-<p>This paragraph has <strong class="bold-style">bold text</strong> with a custom class and <em class="italic-style">italic text</em> with another class.</p>
-<p>You can combine <strong class="bold">bold</strong> and <em class="italic">italic</em> in the same paragraph with different styles.</p>
-<p>Nested <strong class="bold-wrapper">bold with <em class="nested-italic">italic</em> inside</strong> works too.</p>
-<h3 id="images-with-inline-ials">Code with Inline IALs</h3>
-<p>Use <code class="code-inline">inline code</code> for code snippets with styling.</p>
-<p>You can have multiple <code class="code-1">code spans</code> and <code class="code-2">more code</code> with different classes.</p>
-<h3 id="emphasis-with-inline-ials">Mixed Inline Elements</h3>
-<p>This paragraph combines a <a href="https://example.com" class="link-class">link</a>, <strong class="bold-class">bold text</strong>, <em class="italic-class">italic text</em>, and <code class="code-class">code</code> all with different IALs.</p>
-<h2 id="code-with-inline-ials">Complex Examples</h2>
-<h3 id="mixed-inline-elements">Multiple IALs in Sequence</h3>
-<p><a href="url1" class="first">First link</a> and <a href="url2" class="second">second link</a> and <a href="url3" class="third">third link</a> all in one paragraph.</p>
-<p><strong class="b1">First bold</strong>, <strong class="b2">second bold</strong>, and <strong class="b3">third bold</strong> text elements.</p>
-<h3 id="complex-examples">IALs with Text After</h3>
-<p><a href="https://example.com" class="button">Click here</a> to visit our website and learn more.</p>
-<p><strong>Important</strong>: This text has an IAL{:.highlight} that isn’t associated with a span or block level element (bold, italics, link, etc.) and is therefore ignored (left in the text).</p>
-<h3 id="multiple-ials-in-sequence">IALs with Duplicate URLs</h3>
-<p>Here’s a <a href="https://example.com">regular link</a> to demonstrate link styling.</p>
-<p><a href="https://example.com" class="button">Click This Button</a></p>
-<p>Both links point to the same URL, but only the second one has the button class.</p>
-<h3 id="ials-with-text-after">IALs with Multiple Attributes</h3>
-<p><a href="url" class="primary large button">Link with multiple classes</a></p>
-<p><strong id="bold-id" class="highlight important">Bold with ID and classes</strong></p>
-<h2 id="ials-with-duplicate-urls">Edge Cases</h2>
-<h3 id="ials-with-multiple-attributes">IAL at End of Paragraph</h3>
-<p>This paragraph ends with a <a href="https://example.com" class="end-link">link</a>.</p>
-<h3 id="edge-cases">IAL with Whitespace</h3>
-<p><a href="url" class="spaced-class">Link</a> works with spaces.</p>
-<h3 id="ial-at-end-of-paragraph">IALs in Lists</h3>
-<ul>
-<li>List item with <a href="url" class="list-link">link</a></li>
-<li>Another item with <strong class="list-bold">bold</strong> text</li>
-<li>Final item with <code class="list-code">code</code></li>
-</ul>
-<h2 id="ial-with-whitespace">Summary</h2>
-<p>IALs provide a powerful way to add HTML attributes to markdown elements:</p>
-<ul>
-<li>Block-level IALs use next-line syntax: <code>{: .class #id}</code></li>
-<li>Inline IALs appear immediately after elements: <code>[link](url){:.class}</code></li>
-<li>Support for IDs, classes, and custom attributes</li>
-<li>Works with headings, paragraphs, lists, blockquotes, links, images, emphasis, and code</li>
-</ul>
-    </div>
-</body>
-</html>

data/ext/apex_ext/apex_src/tests/include_code.py DELETED Viewed

@@ -1,19 +0,0 @@
-#!/usr/bin/env python3
-"""Example code for inclusion"""
-def process_document(filename):
-    """Process a markdown document"""
-    with open(filename, 'r') as f:
-        content = f.read()
-    return convert_markdown(content)
-def convert_markdown(text):
-    """Convert markdown to HTML"""
-    processor = MarkdownProcessor()
-    return processor.render(text)
-if __name__ == '__main__':
-    import sys
-    result = process_document(sys.argv[1])
-    print(result)

data/ext/apex_ext/apex_src/tests/include_snippet.md DELETED Viewed

@@ -1,15 +0,0 @@
-### Included Content
-This content was **included** from an external file. It
-demonstrates:
-- File inclusion feature
-- Recursive markdown processing
-- Path resolution
-You can include this in other documents seamlessly!
-This is line 11. It contains the pattern 1234567.
-This is line 12.
-This is line 13.
-Z: This is line 14. it includes a prefix.

data/ext/apex_ext/apex_src/tests/metadata_cli_test.sh DELETED Viewed

@@ -1,119 +0,0 @@
-#!/usr/bin/env bash
-# CLI tests for --info, --extract-meta, and --extract-meta-value using tests/fixtures/metadata.
-set -euo pipefail
-ROOT="$(cd "$(dirname "${BASH_SOURCE[0]}")/.." && pwd)"
-APEX_BIN="${APEX_BIN:-$ROOT/build/apex}"
-FIXTURES="$ROOT/tests/fixtures/metadata"
-YAML="$FIXTURES/yaml-frontmatter.md"
-MMD="$FIXTURES/mmd-metadata.md"
-PANDOC="$FIXTURES/pandoc-meta.md"
-if [[ ! -x "$APEX_BIN" ]]; then
-	echo "Error: $APEX_BIN not found or not executable. Build Apex first (cmake --build build --target apex_cli)." >&2
-	exit 1
-fi
-for f in "$YAML" "$MMD" "$PANDOC"; do
-	if [[ ! -f "$f" ]]; then
-		echo "Error: missing fixture $f" >&2
-		exit 1
-	fi
-done
-TMPDIR="${TMPDIR:-/tmp}"
-WORK="$(mktemp -d "${TMPDIR}/apex-metadata-cli-XXXXXX")"
-trap 'rm -rf "$WORK"' EXIT
-echo "== Testing -i / --info (no input files; info on stdout) =="
-INFO_OUT="$WORK/info_stdout.txt"
-# Close stdin so the CLI does not wait for interactive input in some environments.
-"$APEX_BIN" -i </dev/null >"$INFO_OUT"
-grep -q '^version:' "$INFO_OUT"
-grep -q 'plugins:' "$INFO_OUT"
-echo "-i without files: stdout contains version and plugins section."
-echo
-echo "== Testing -i with a file (info on stderr, HTML on stdout) =="
-STDOUT="$WORK/out.html"
-STDERR="$WORK/info.err"
-"$APEX_BIN" -i "$YAML" >"$STDOUT" 2>"$STDERR"
-grep -q '^version:' "$STDERR" || {
-	echo "metadata_cli_test: expected version line on stderr when using -i with a file" >&2
-	exit 1
-}
-grep -q '<p>' "$STDOUT" || {
-	echo "metadata_cli_test: expected HTML fragment on stdout with -i and a file" >&2
-	exit 1
-}
-echo "-i with file: version/config on stderr, conversion on stdout."
-echo
-echo "== Testing --extract-meta (YAML fixture) =="
-META_OUT="$WORK/meta.yaml"
-"$APEX_BIN" --extract-meta "$YAML" >"$META_OUT"
-grep -q '^title: A YAML test$' "$META_OUT" || {
-	echo "metadata_cli_test: --extract-meta missing expected title from YAML fixture" >&2
-	exit 1
-}
-grep -q '^random_key: Flargle$' "$META_OUT" || {
-	echo "metadata_cli_test: --extract-meta missing random_key from YAML fixture" >&2
-	exit 1
-}
-echo "--extract-meta on YAML front matter: expected keys present."
-echo
-echo "== Testing -e / --extract-meta-value =="
-val="$("$APEX_BIN" -e title "$YAML")"
-if [[ "$val" != "A YAML test" ]]; then
-	echo "metadata_cli_test: -e title from YAML expected 'A YAML test', got '$val'" >&2
-	exit 1
-fi
-val="$("$APEX_BIN" --extract-meta-value random_key "$YAML")"
-if [[ "$val" != "Flargle" ]]; then
-	echo "metadata_cli_test: -e random_key expected 'Flargle', got '$val'" >&2
-	exit 1
-fi
-val="$("$APEX_BIN" -e randomkey "$MMD")"
-if [[ "$val" != "Bargle" ]]; then
-	echo "metadata_cli_test: -e randomkey (MMD) expected 'Bargle', got '$val'" >&2
-	exit 1
-fi
-val="$("$APEX_BIN" -e title "$PANDOC")"
-if [[ "$val" != "Pandoc Metadata" ]]; then
-	echo "metadata_cli_test: -e title (Pandoc) expected 'Pandoc Metadata', got '$val'" >&2
-	exit 1
-fi
-if "$APEX_BIN" -e definitely_missing_key_xyz "$YAML" 2>"$WORK/miss.err"; then
-	echo "metadata_cli_test: expected non-zero exit for missing metadata key" >&2
-	exit 1
-fi
-grep -q "not found" "$WORK/miss.err" || {
-	echo "metadata_cli_test: expected error message for missing key on stderr" >&2
-	exit 1
-}
-echo "-e returns values and exit 1 when key is absent."
-echo
-echo "== Testing --combine --extract-meta (merge order, later file wins) =="
-COMBINED="$WORK/combined_meta.yaml"
-"$APEX_BIN" --combine --extract-meta "$MMD" "$YAML" >"$COMBINED"
-grep -q '^title: A YAML test$' "$COMBINED" || {
-	echo "metadata_cli_test: combined extract expected last file to win for title" >&2
-	exit 1
-}
-echo "--combine --extract-meta: later file overrides title as expected."
-echo
-echo "All metadata CLI tests passed."

data/ext/apex_ext/apex_src/tests/multi_file_cli_test.sh DELETED Viewed

@@ -1,64 +0,0 @@
-#!/usr/bin/env bash
-# Simple CLI-level sanity tests for --mmd-merge and --combine (GitBook SUMMARY.md)
-# using the existing combine_summary fixtures.
-set -euo pipefail
-ROOT="$(cd "$(dirname "${BASH_SOURCE[0]}")/.." && pwd)"
-APEX_BIN="$ROOT/build/apex"
-if [[ ! -x "$APEX_BIN" ]]; then
-	echo "Error: $APEX_BIN not found or not executable. Build Apex first (cmake --build build)." >&2
-	exit 1
-fi
-FIXTURES="$ROOT/tests/fixtures/combine_summary"
-TMPDIR="$(mktemp -d "${TMPDIR:-/tmp}/apex-multi-file-XXXXXX")"
-trap 'rm -rf "$TMPDIR"' EXIT
-echo "== Testing --mmd-merge with mmd_merge-style index =="
-MMD_OUT="$TMPDIR/mmd_merge_output.md"
-"$APEX_BIN" --mmd-merge "$FIXTURES/index.txt" >"$MMD_OUT"
-# Expect Intro, Chapter 1, and Section 1.1 in order, with Section 1.1 headings shifted one level
-grep -q '^# Intro' "$MMD_OUT" || {
-	echo "mmd-merge: missing Intro heading"
-	exit 1
-}
-grep -q '^# Chapter 1' "$MMD_OUT" || {
-	echo "mmd-merge: missing Chapter 1 heading"
-	exit 1
-}
-grep -q '^## Section 1\.1' "$MMD_OUT" || {
-	echo "mmd-merge: Section 1.1 heading was not shifted to level 2"
-	exit 1
-}
-echo "mmd-merge index test passed."
-echo
-echo "== Testing --combine with GitBook-style SUMMARY.md =="
-COMBINE_OUT="$TMPDIR/summary_combine_output.md"
-"$APEX_BIN" --combine "$FIXTURES/SUMMARY.md" >"$COMBINE_OUT"
-grep -q '^# Intro' "$COMBINE_OUT" || {
-	echo "combine: missing Intro heading from SUMMARY.md combine"
-	exit 1
-}
-grep -q '^# Chapter 1' "$COMBINE_OUT" || {
-	echo "combine: missing Chapter 1 heading from SUMMARY.md combine"
-	exit 1
-}
-grep -q '^# Section 1\.1' "$COMBINE_OUT" || {
-	echo "combine: missing Section 1.1 heading from SUMMARY.md combine"
-	exit 1
-}
-echo "SUMMARY.md combine test passed."
-echo
-echo "All multi-file CLI tests passed."

data/ext/apex_ext/apex_src/tests/paginate_cli_test.sh DELETED Viewed

@@ -1,80 +0,0 @@
-#!/usr/bin/env bash
-# Sanity checks for -p/--paginate and paginate config option for terminal output.
-set -euo pipefail
-ROOT="$(cd "$(dirname "${BASH_SOURCE[0]}")/.." && pwd)"
-APEX_BIN="${APEX_BIN:-$ROOT/build/apex}"
-if [[ ! -x "$APEX_BIN" ]]; then
-	echo "Error: $APEX_BIN not found or not executable. Set APEX_BIN or build first." >&2
-	exit 1
-fi
-DOC="# Heading
-Some *styled* text for testing."
-echo "== Testing --paginate with APEX_PAGER=cat =="
-BASE_OUT=$("$APEX_BIN" -t terminal <<< "$DOC")
-PAGED_OUT=$(APEX_PAGER=cat "$APEX_BIN" -t terminal --paginate <<< "$DOC")
-if [[ "$BASE_OUT" != "$PAGED_OUT" ]]; then
-	echo "paginate_cli_test: -p output differs from baseline when using APEX_PAGER=cat" >&2
-	exit 1
-fi
-echo "paginate_cli_test: -p with APEX_PAGER=cat matches baseline output."
-echo
-echo "== Testing paginate: true via config metadata with APEX_PAGER=cat =="
-TMPDIR="$(mktemp -d "${TMPDIR:-/tmp}/apex-paginate-XXXXXX")"
-trap 'rm -rf "$TMPDIR"' EXIT
-CFG="$TMPDIR/config.yml"
-cat >"$CFG" <<'YAML'
-paginate: true
-YAML
-CFG_OUT=$(APEX_PAGER=cat "$APEX_BIN" --meta-file "$CFG" -t terminal <<< "$DOC")
-if [[ "$BASE_OUT" != "$CFG_OUT" ]]; then
-	echo "paginate_cli_test: paginate: true output differs from baseline when using APEX_PAGER=cat" >&2
-	exit 1
-fi
-echo "paginate_cli_test: paginate: true config matches baseline output with APEX_PAGER=cat."
-echo
-echo "== Testing paginate: symbols via config metadata with APEX_PAGER=cat =="
-CFG_SYM="$TMPDIR/config-symbols.yml"
-cat >"$CFG_SYM" <<'YAML'
-paginate: symbols
-YAML
-SYM_OUT=$(APEX_PAGER=cat "$APEX_BIN" --meta-file "$CFG_SYM" -t terminal <<< "$DOC")
-if [[ "$BASE_OUT" != "$SYM_OUT" ]]; then
-	echo "paginate_cli_test: paginate: symbols output differs from baseline when using APEX_PAGER=cat" >&2
-	exit 1
-fi
-echo "paginate_cli_test: paginate: symbols config matches baseline output with APEX_PAGER=cat."
-echo
-echo "== Testing that --paginate is ignored for non-terminal formats =="
-HTML_BASE=$("$APEX_BIN" -t html <<< "$DOC")
-HTML_PAGED=$(APEX_PAGER=cat "$APEX_BIN" -t html --paginate <<< "$DOC")
-if [[ "$HTML_BASE" != "$HTML_PAGED" ]]; then
-	echo "paginate_cli_test: -p should be a no-op for -t html" >&2
-	exit 1
-fi
-echo "paginate_cli_test: -p ignored for non-terminal formats as expected."
-echo
-echo "All paginate CLI tests passed."

data/ext/apex_ext/apex_src/tests/sample_data.csv DELETED Viewed

@@ -1,7 +0,0 @@
-Product,Q1 Sales,Q2 Sales,Q3 Sales,Q4 Sales,Total
-Widget A,25000,28000,32000,35000,120000
-Widget B,18000,22000,25000,28000,93000
-Widget C,32000,35000,38000,42000,147000
-Service X,45000,48000,52000,58000,203000
-Service Y,28000,31000,34000,38000,131000

data/ext/apex_ext/apex_src/tests/table_escaped_ltlt.md DELETED Viewed

@@ -1,4 +0,0 @@
-| A   | B   | C   |
-| --- | --- | --- |
-| D   | <<  | <<  |
-| E   | \<< | F   |

data/ext/apex_ext/apex_src/tests/terminal_width_test.sh DELETED Viewed

@@ -1,29 +0,0 @@
-#!/usr/bin/env bash
-# Sanity check that -t terminal --width N wraps output (CLI applies wrap after render).
-set -euo pipefail
-ROOT="$(cd "$(dirname "${BASH_SOURCE[0]}")/.." && pwd)"
-APEX_BIN="${APEX_BIN:-$ROOT/build/apex}"
-if [[ ! -x "$APEX_BIN" ]]; then
-	echo "Error: $APEX_BIN not found or not executable. Set APEX_BIN or build first." >&2
-	exit 1
-fi
-# Long line without ANSI: with --width 10 we expect more than one line
-LONG="this is a long line of plain text that should wrap"
-OUT=$("$APEX_BIN" -t terminal --width 10 <<< "$LONG")
-LINES=$(echo "$OUT" | wc -l | tr -d ' ')
-if [[ "$LINES" -lt 2 ]]; then
-	echo "Expected --width 10 to wrap output into multiple lines, got $LINES line(s)" >&2
-	exit 1
-fi
-# With --width 80 the same line may stay on one line (or wrap less)
-OUT2=$("$APEX_BIN" -t terminal --width 80 <<< "$LONG")
-if [[ -z "$OUT2" ]]; then
-	echo "Expected non-empty output with --width 80" >&2
-	exit 1
-fi
-echo "terminal_width_test: --width wrapping OK"

data/ext/apex_ext/apex_src/tests/test-swift-package.sh DELETED Viewed

@@ -1,14 +0,0 @@
-#!/usr/bin/env bash
-set -euo pipefail
-ROOT="$(cd "$(dirname "${BASH_SOURCE[0]}")/.." && pwd)"
-cd "$ROOT"
-echo "=== Swift debug build ==="
-swift build
-echo "=== Swift release build ==="
-swift build -c release
-echo "Swift package OK."