Troubleshooting Guide

This guide helps you diagnose and resolve common issues when working with putior. Each section covers a specific category of problems with practical solutions.

Most Common Issues - Start here!
Quick Diagnostics
Annotation Syntax Errors
File Pattern Matching Issues
Diagram Rendering Problems
Multi-Language Support Issues
Performance Tips
Debugging with Logging
FAQ
Getting Help

Most Common Issues

These are the top 5 issues users encounter. Check these first!

1. Annotations Not Detected

Frequency: 🔴 Very Common

Problem: put() returns an empty data frame even though you have annotations in your files.

Cause: Wrong comment prefix for your file type.

Solution: Use the correct comment prefix for your language:

Language	Correct Prefix	Example
R, Python	`# put`	`# put label:"Step 1"`
SQL, Lua	`-- put`	`-- put label:"Step 1"`
JavaScript, Go, C	`// put`	`// put label:"Step 1"`
MATLAB	`% put`	`% put label:"Step 1"`

# Check what prefix your file type needs
get_comment_prefix("sql")  # Returns "--"
get_comment_prefix("js")   # Returns "//"

2. Nodes Not Connecting in Diagram

Frequency: 🔴 Very Common

Problem: Diagram shows isolated nodes instead of a connected workflow.

Cause: Typo in input/output names - they must match exactly.

Solution: Check that output of one node matches input of the next:

# WRONG - Names don't match
# put id:"step1", output:"data.csv"      # Outputs "data.csv"
# put id:"step2", input:"Data.csv"       # Expects "Data.csv" (case mismatch!)

# CORRECT - Exact match
# put id:"step1", output:"data.csv"
# put id:"step2", input:"data.csv"

Diagnostic:

workflow <- put("./src/")
# Check for mismatches
unique(workflow$output)
unique(workflow$input)

3. Diagram Not Rendering

Frequency: 🟡 Occasional

Problem: Mermaid code appears as text instead of a diagram.

Cause: Mermaid.js not loaded, or syntax error in generated code.

Solution:

For pkgdown sites: Ensure Mermaid is included in _pkgdown.yml
For R Markdown: Use raw output and a Mermaid-enabled viewer
Quick test: Paste the output into mermaid.live

# Get raw Mermaid code to debug
mermaid_code <- put_diagram(workflow, output = "raw")
cat(mermaid_code)  # Copy this to mermaid.live to test

4. Auto-Detection Missing Expected Patterns

Frequency: 🟡 Occasional

Problem: put_auto() doesn’t detect file reads/writes you expected.

Cause: Library or function not in detection patterns.

Solution:

Check if your library is supported:

patterns <- get_detection_patterns("r")
# Search for your function
grep("readr", sapply(patterns$input, `[[`, "func"), value = TRUE)

Use manual annotations for unsupported patterns
Request new patterns via GitHub issue

5. Wrong Language Detection

Frequency: 🟢 Rare

Problem: File parsed with wrong comment syntax.

Cause: Unusual file extension or ambiguous extension (e.g., .m for MATLAB vs Objective-C).

Solution:

# Check what language is detected for your extension
ext_to_language("m")   # Returns "matlab"
ext_to_language("jl")  # Returns "julia"

# List all supported extensions
get_supported_extensions()

If your extension isn’t recognized, use the standard extension or add manual annotations with the correct comment prefix.

Quick Diagnostics

Before diving into specific issues, run these quick checks:

library(putior)

# 1. Check if annotations are found
workflow <- put("./src/", validate = TRUE, include_line_numbers = TRUE)
nrow(workflow)  # Should be > 0 if annotations exist

# 2. Test a single annotation
is_valid_put_annotation('# put id:"test", label:"Test Node"')  # Should be TRUE

# 3. Check supported extensions
get_supported_extensions()

# 4. Enable detailed logging
set_putior_log_level("DEBUG")
workflow <- put("./src/")  # Now shows detailed output

Annotation Syntax Errors

Missing or Mismatched Quotes

Problem: Annotation is not recognized or properties are missing.

# WRONG - No quotes around values
# put id:my_node, label:My Process

# WRONG - Mismatched quotes
# put id:"my_node', label:"My Process"

# WRONG - Missing closing quote
# put id:"my_node, label:"My Process"

Solution: Always use matching quotes around all values.

# CORRECT - Double quotes
# put id:"my_node", label:"My Process"

# CORRECT - Single quotes
# put id:'my_node', label:'My Process'

# CORRECT - Mixed (but consistent per value)
# put id:"my_node", label:'My Process'

# CORRECT - The other kind of quote inside a value
# put id:"my_node", label:"Don't panic"
# put id:"my_node", label:'Say "hi"'

A value cannot contain the kind of quote it is wrapped in; there are no escapes. put() warns about each property it cannot read (“Ignored label:…”) unless validate = FALSE.

Diagnostic:

# Test your annotation syntax
is_valid_put_annotation('# put id:"my_node", label:"My Process"')  # TRUE
is_valid_put_annotation('# put id:my_node, label:My Process')      # FALSE

Invalid Node Types

Problem: Validation warning about unusual node_type.

# Triggers warning - non-standard type
# put id:"step1", label:"Process", node_type:"transform"

Solution: Use standard node types for consistency.

# Standard node types
# put id:"step1", label:"Load Data", node_type:"input"
# put id:"step2", label:"Transform", node_type:"process"
# put id:"step3", label:"Save Results", node_type:"output"
# put id:"step4", label:"Check Quality", node_type:"decision"
# put id:"step5", label:"Start Pipeline", node_type:"start"
# put id:"step6", label:"End Pipeline", node_type:"end"

Note: Custom node types work but generate warnings. Suppress with validate = FALSE:

workflow <- put("./src/", validate = FALSE)

Commas Inside Values

Problem: Values containing commas are truncated.

# WRONG - Comma breaks the label
# put id:"step1", label:Load, clean, transform data

Solution: Enclose values with commas in quotes.

# CORRECT - Quotes protect the comma
# put id:"step1", label:"Load, clean, transform data"

Empty or Missing IDs

Problem: Warning about empty ID.

# WRONG - Empty ID string
# put id:"", label:"My Process"

# OK - Missing ID (generated automatically)
# put label:"My Process"

Solution: Either omit the ID entirely (auto-generated) or provide a valid one.

# With auto-generated ID
workflow <- put("./src/")
print(workflow$id)  # UUIDs like "a1b2c3d4-...", or "node_1", ... without uuid

# With explicit IDs
# put id:"step1", label:"First Step"
# put id:"step2", label:"Second Step"

Duplicate IDs

Problem: Warning about duplicate node IDs.

# In file1.R
# put id:"load_data", label:"Load from CSV"

# In file2.R
# put id:"load_data", label:"Load from JSON"  # DUPLICATE!

Solution: Use unique IDs across all files in your workflow.

# In file1.R
# put id:"load_csv", label:"Load from CSV"

# In file2.R
# put id:"load_json", label:"Load from JSON"

Multiline Annotation Issues

Problem: Multiline annotations not being parsed correctly.

# WRONG - Missing backslash
# put id:"step1", label:"Process",
#     input:"data.csv", output:"results.csv"

# WRONG - Backslash not at end of line
# put id:"step1", label:"Process", \
#     input:"data.csv"

# WRONG - Missing comment prefix on continuation
# put id:"step1", label:"Process", \
    input:"data.csv"

Solution: Use proper multiline syntax.

# CORRECT - Backslash at end, comment prefix on each line
# put id:"step1", label:"Process Data", \
#     input:"data.csv,config.json", \
#     output:"results.csv"

For SQL files:

-- put id:"etl_job", label:"ETL Process", \
--     input:"source_table", \
--     output:"target_table"

For JavaScript files:

// put id:"handler", label:"API Handler", \
//     input:"request.json", \
//     output:"response.json"

File Pattern Matching Issues

Files Not Found

Problem: put() returns empty result or “no files found” warning.

workflow <- put("./src/")
#> Warning: No files matching pattern '\.(R|r|py|sql|sh|jl)$' found in: ./src/

Diagnostic Steps:

# 1. Check if directory exists
dir.exists("./src/")

# 2. List files in directory
list.files("./src/", recursive = TRUE)

# 3. Check what patterns match
list.files("./src/", pattern = "\\.(R|r|py)$")

Solutions:

# Use correct path (absolute or relative)
workflow <- put("/full/path/to/src/")

# Scan recursively for subdirectories
workflow <- put("./src/", recursive = TRUE)

# Check if single file path works
workflow <- put("./src/script.R")

Wrong File Extensions

Problem: Your files use extensions not in the default pattern.

# Default pattern only matches: R, r, py, sql, sh, jl
workflow <- put("./src/")  # Won't find .js, .ts, .go files

Solution: Specify a custom pattern for your file types.

# JavaScript/TypeScript files
workflow <- put("./src/", pattern = "\\.(js|ts|jsx|tsx)$")

# Go files
workflow <- put("./src/", pattern = "\\.go$")

# Rust files
workflow <- put("./src/", pattern = "\\.rs$")

# Multiple languages
workflow <- put("./src/", pattern = "\\.(R|py|js|ts|go|rs)$")

# All supported extensions
all_exts <- paste(get_supported_extensions(), collapse = "|")
pattern <- paste0("\\.(", all_exts, ")$")
workflow <- put("./src/", pattern = pattern)

Case Sensitivity

Problem: Files not found due to case mismatch.

# Pattern is case-sensitive by default
list.files("./src/", pattern = "\\.R$")   # Finds script.R
list.files("./src/", pattern = "\\.r$")   # Finds script.r

Solution: Include both cases in pattern.

# Match both .R and .r
workflow <- put("./src/", pattern = "\\.(R|r)$")

# Or use the default pattern which includes both
workflow <- put("./src/")  # Default: "\\.(R|r|py|sql|sh|jl)$"

Diagram Rendering Problems

Mermaid Syntax Errors

Problem: Diagram doesn’t render or shows syntax error.

Diagnostic:

# Get raw Mermaid code to inspect
workflow <- put("./src/")
mermaid_code <- put_diagram(workflow, output = "raw")
cat(mermaid_code)

Common Causes:

Quotes in labels: put_diagram() escapes quotes and other characters that Mermaid would misread, so a label may contain them. In the annotation, wrap such a label in the other kind of quote.

# Problem: the label's own quotes end the value, so put() ignores it
# put id:"step1", label:"Load "raw" data"

# Solution: wrap the label in the other kind of quote
# put id:"step1", label:'Load "raw" data'
# put id:"step1", label:"Load 'raw' data"

Mermaid keywords as IDs: ids such as end or class are Mermaid keywords. put_diagram() writes them as node_end and node_class, so they work; only the id in the Mermaid code differs.

Label Loses Text After `<`

Problem: Part of a label is missing, and put_diagram() warned that a label contains a < before a letter, /, ! or ?.

Cause: Mermaid draws labels as HTML, so < followed by a letter (or by /, ! or ?) starts an HTML tag. A tag it does not know, such as <draft>, disappears, and so does text that looks like the attributes of a real tag: a<b and c>d shows “ad”.

Solution: Write < for a < that should show:

# put id:"filter", label:"Keep rows with n &lt;threshold"

A < followed by a space, a digit or - (x < 5, x<5, x <- y) shows as written. Inside $$...$$ math, write \lt: < and a plain < make KaTeX fail. Labels may still contain the tags br, b, i, em, strong, sub, sup, code and span on purpose; put_diagram() does not warn about them. Give their attributes single quotes (<span style='color:red'>).

Title Shows `<` or Loses Text

Problem: The title above the diagram shows <, > or &, or part of it is missing, and put_diagram() warned that the title contains <.

Cause: Mermaid passes the title through an HTML sanitizer. When the title contains a <, the drawn title shows HTML entities such as <, > and & for <, > and &, and text that looks like an HTML tag (such as <draft>) disappears. No escape avoids that.

Solution: Leave the < out of the title, or write “less than”. The title that screen readers announce (accTitle) shows it as written.

Theme Issues

Problem: Diagram colors don’t appear or look wrong.

# Check available themes
get_diagram_themes()
#> $light, $dark, $auto, $minimal, $github
#> $viridis, $magma, $plasma, $cividis (colorblind-safe)

Solutions:

# Try a different theme
put_diagram(workflow, theme = "github")
put_diagram(workflow, theme = "minimal")

# Disable node styling for plain diagrams
put_diagram(workflow, style_nodes = FALSE)

# Check if theme is compatible with your viewer
# "github" works best on GitHub README
# "dark" for dark mode applications
# "minimal" for printing/PDFs
# "viridis", "magma", "plasma", "cividis" for colorblind accessibility

Missing Connections

Problem: Nodes appear but arrows don’t connect them.

Cause: Input/output values don’t match between nodes.

# Problem: Typo in file name
# put id:"step1", output:"data.csv"
# put id:"step2", input:"Data.csv"  # Case mismatch!

# Solution: Match exactly
# put id:"step1", output:"data.csv"
# put id:"step2", input:"data.csv"

Diagnostic:

# Check what inputs and outputs are defined
workflow <- put("./src/")
print(workflow[, c("id", "input", "output")])

Artifacts Not Showing

Problem: Data files (artifacts) don’t appear in diagram.

# Enable artifacts display
put_diagram(workflow, show_artifacts = TRUE)

# Artifacts are intermediate files that connect nodes
# They're hidden by default for cleaner diagrams

Large Diagram Shows an Error or a Placeholder

Problem: A large workflow’s diagram is replaced by “Edge limit exceeded”, “Syntax error in text” or a one-node “Maximum text size in diagram exceeded” placeholder.

Mermaid draws at most 500 edges and 50,000 characters by default (maxEdges, maxTextSize). Both are settings that only the page can change (mermaid.initialize()); a diagram cannot raise them, and GitHub, GitLab and Quarto keep the defaults. put_diagram() warns when its output is over either limit.

Solutions:

# Fewer edges: leave out the file nodes
put_diagram(workflow, show_artifacts = FALSE)

# A smaller workflow: skip files, or draw a subset of the steps
workflow <- put("./src/", exclude = "legacy/")
put_diagram(workflow[workflow$file_name %in% c("load.R", "clean.R"), ])

# Less text: shorter labels, no styling lines
put_diagram(workflow, node_labels = "name", style_nodes = FALSE)

Multi-Language Support Issues

Wrong Comment Prefix Detected

Problem: Annotations not found in SQL, JavaScript, or other files.

Cause: Using wrong comment syntax for the language.

-- WRONG for SQL - using hash instead of dash
# put id:"query", label:"Run Query"

-- CORRECT for SQL
-- put id:"query", label:"Run Query"

// WRONG for JavaScript - using hash
# put id:"handler", label:"Handle Request"

// CORRECT for JavaScript
// put id:"handler", label:"Handle Request"

Check the correct prefix:

# Get comment prefix for any extension
get_comment_prefix("sql")   # "--"
get_comment_prefix("js")    # "//"
get_comment_prefix("m")     # "%"
get_comment_prefix("py")    # "#"
get_comment_prefix("go")    # "//"
get_comment_prefix("rs")    # "//"

Reference Table

Extension	Comment Prefix	Example
`.R`, `.r`	`#`	`# put id:"step", label:"Process"`
`.py`	`#`	`# put id:"step", label:"Process"`
`.sql`	`--`	`-- put id:"query", label:"Query"`
`.js`, `.ts`	`//`	`// put id:"func", label:"Function"`
`.go`	`//`	`// put id:"main", label:"Main"`
`.rs`	`//`	`// put id:"fn", label:"Handler"`
`.m` (MATLAB)	`%`	`% put id:"calc", label:"Compute"`
`.tex`	`%`	`% put id:"sec", label:"Section"`
`.sh`	`#`	`# put id:"cmd", label:"Command"`
`.lua`	`--`	`-- put id:"fn", label:"Function"`

Unsupported Extension

Problem: File type not automatically recognized.

# Check if extension is supported
ext <- "xyz"
get_comment_prefix(ext)  # Returns "#" as fallback

# List all supported extensions
get_supported_extensions()

Escape Hatches for Unsupported File Types:

Option 1: Use fallback # prefix (if your language supports # comments)

# In your .xyz file (if it supports # comments)
# put id:"step1", label:"Process Data"

Option 2: Create a wrapper annotation file

# workflow-annotations.R
# This file documents the workflow for unsupported file types

# put id:"xyz_step1", label:"Process in XYZ format", input:"data.xyz", output:"result.xyz"
# put id:"xyz_step2", label:"Convert output", input:"result.xyz", output:"final.csv"

# Then scan this file instead
workflow <- put("workflow-annotations.R")

Option 3: Use text input for ad-hoc annotations

# Define workflow without files
workflow <- put(text = '
# put id:"step1", label:"Custom Step 1", output:"data.xyz"
# put id:"step2", label:"Custom Step 2", input:"data.xyz"
')
put_diagram(workflow)

Option 4: Request new language support

Open a GitHub issue with: - Language name and file extension - Comment syntax used by the language - Example code showing typical file I/O patterns (for auto-detection)

Performance Tips for Large Codebases

Slow Scanning

Problem: put() takes too long on large projects.

Solutions:

# 1. Limit to specific directories
workflow <- put("./src/core/")  # Instead of ./

# 2. Use specific file patterns
workflow <- put("./src/", pattern = "\\.R$")  # Only R files

# 3. Limit to top-level directory if subdirs not needed
workflow <- put("./src/", recursive = FALSE)

# 4. Disable validation for faster scanning
workflow <- put("./src/", validate = FALSE)

Memory Issues with Large Workflows

Problem: Many nodes cause memory or rendering issues.

Solutions:

# 1. Split into smaller subgraphs
workflow_etl <- put("./src/etl/")
workflow_ml <- put("./src/ml/")

# Generate separate diagrams
put_diagram(workflow_etl, file = "etl_workflow.md")
put_diagram(workflow_ml, file = "ml_workflow.md")

# 2. Hide artifacts for cleaner diagrams
put_diagram(workflow, show_artifacts = FALSE)

# 3. Use simpler theme
put_diagram(workflow, theme = "minimal", style_nodes = FALSE)

Reducing Annotation Overhead

Best Practices:

# Annotate key steps only, not every function
# Good: Major pipeline stages
# put id:"ingest", label:"Data Ingestion", node_type:"input"
# put id:"transform", label:"Data Transformation", node_type:"process"
# put id:"export", label:"Export Results", node_type:"output"

# Avoid: Every small helper function
# (Don't annotate utility functions unless they're significant)

Debugging with Logging

Enable Detailed Logging

# Install logger package (optional but recommended)
install.packages("logger")

# Set log level
set_putior_log_level("DEBUG")  # Maximum detail
set_putior_log_level("INFO")   # Progress updates
set_putior_log_level("WARN")   # Issues only (default)
set_putior_log_level("ERROR")  # Fatal errors only

Per-Call Logging

# Override log level for a single call
workflow <- put("./src/", log_level = "DEBUG")
put_diagram(workflow, log_level = "INFO")

What Each Level Shows

Level	Information Shown
`DEBUG`	File-by-file processing, pattern matching, parsing steps
`INFO`	Scan started, files found, nodes extracted, diagram generated
`WARN`	Validation issues, missing dependencies
`ERROR`	Fatal errors that stop execution

Debugging Example

# Problem: Annotations not being found

# 1. Enable debug logging
set_putior_log_level("DEBUG")

# 2. Run the scan
workflow <- put("./problem_file.R", include_line_numbers = TRUE)

# 3. Check the logs for:
#    - "No PUT annotations found in..." (wrong syntax?)
#    - "Found X PUT annotation(s)..." (they exist!)
#    - "Processing file:..." (file is being scanned)

# 4. Reset to normal
set_putior_log_level("WARN")

Logger Not Installed

If you don’t have the logger package installed, putior works silently without logging. Install it for debugging:

install.packages("logger")

# Verify it's working
library(logger)
set_putior_log_level("INFO")
workflow <- put("./src/")
#> INFO [2024-01-15 10:30:00] Starting PUT annotation scan
#> INFO [2024-01-15 10:30:00] Found 3 file(s) to scan
#> INFO [2024-01-15 10:30:01] Scan complete: found 5 workflow node(s)

Frequently Asked Questions

Q: Why are my annotations not found?

A: Check these common causes:

Wrong comment prefix for file type (see Multi-Language Support)
Missing quotes around property values
File not matching pattern (check list.files())
Typo in “put” keyword (must be lowercase: # put not # PUT)

# Validate syntax
is_valid_put_annotation('# put id:"test", label:"Test"')  # TRUE
is_valid_put_annotation('# PUT id:"test", label:"Test"')  # FALSE (uppercase)

Q: How do I connect nodes between files?

A: Use matching input/output file names:

# In 01_load.R
# put id:"load", label:"Load Data", output:"raw_data.csv"

# In 02_process.R
# put id:"process", label:"Process", input:"raw_data.csv", output:"clean_data.csv"

Q: What if I don’t specify an output?

A: putior automatically uses the file name as the output.

# In process_data.R
# put id:"process", label:"Process Data", input:"raw.csv"
# Output defaults to "process_data.R"

# In analyze.R
# put id:"analyze", label:"Analyze", input:"process_data.R"
# This creates a connection from process_data.R to analyze.R

Q: Can I use putior in CI/CD?

A: Yes, putior works in headless environments:

# Generate diagram file for documentation
workflow <- put("./src/", recursive = TRUE)
put_diagram(workflow,
            output = "file",
            file = "docs/workflow.md",
            theme = "github")

Q: How do I track in-memory variables?

A: Use the .internal extension:

# Variables created during script execution
# put id:"create", output:"dataset.internal, dataset.RData"
dataset <- data.frame(x = 1:100)
save(dataset, file = "dataset.RData")

# Next script uses the saved file, not .internal
# put id:"analyze", input:"dataset.RData", output:"results.internal"
load("dataset.RData")
results <- summary(dataset)

Important: .internal files can only be outputs, never inputs between scripts.

Q: Why does the diagram look different on GitHub vs locally?

A: Different Mermaid renderers interpret themes differently.

# For GitHub README
put_diagram(workflow, theme = "github")

# For local HTML
put_diagram(workflow, theme = "light")

# For universal compatibility
put_diagram(workflow, theme = "minimal", style_nodes = FALSE)

Q: Can I use custom properties?

A: Yes, putior preserves any properties you define:

# put id:"train", label:"Train Model", \
#     node_type:"process", \
#     runtime:"2h", \
#     gpu:"required", \
#     priority:"high"

workflow <- put("./src/")
print(workflow$runtime)   # "2h"
print(workflow$gpu)       # "required"
print(workflow$priority)  # "high"

Q: How do I suppress validation warnings?

A: Disable validation:

# Suppress all validation warnings
workflow <- put("./src/", validate = FALSE)

# Or suppress specific warnings with suppressWarnings()
workflow <- suppressWarnings(put("./src/"))

Getting Help

If you’re still stuck:

Check the vignettes:
- Quick Start - First diagram in 2 minutes
- Annotation Guide - Complete syntax reference
- Quick Reference - Cheat sheet
- Features Tour - Advanced features
- API Reference - Complete function docs

Use the sandbox:

run_sandbox()  # Interactive experimentation

Enable debug logging and check output carefully
Report issues on GitHub with:
- R version (R.version.string)
- putior version (packageVersion("putior"))
- Minimal reproducible example
- Debug log output

# Gather diagnostic info
sessionInfo()
packageVersion("putior")
get_supported_extensions()

Guide	Description
Quick Start	First diagram in 2 minutes
Annotation Guide	Complete syntax reference
Features Tour	Auto-detection, themes, logging
API Reference	Function documentation
Showcase	Real-world examples
Quick Reference	At-a-glance reference card
AI Integration	MCP/ACP integration guide

Troubleshooting Guide

Contents

Most Common Issues

1. Annotations Not Detected

2. Nodes Not Connecting in Diagram

3. Diagram Not Rendering

4. Auto-Detection Missing Expected Patterns

5. Wrong Language Detection

Quick Diagnostics

Annotation Syntax Errors

Missing or Mismatched Quotes

Invalid Node Types

Commas Inside Values

Empty or Missing IDs

Duplicate IDs

Multiline Annotation Issues

File Pattern Matching Issues

Files Not Found

Wrong File Extensions

Case Sensitivity

Diagram Rendering Problems

Mermaid Syntax Errors

Label Loses Text After <

Title Shows &lt; or Loses Text

Theme Issues

Missing Connections

Artifacts Not Showing

Large Diagram Shows an Error or a Placeholder

Multi-Language Support Issues

Wrong Comment Prefix Detected

Reference Table

Unsupported Extension

Performance Tips for Large Codebases

Slow Scanning

Memory Issues with Large Workflows

Reducing Annotation Overhead

Debugging with Logging

Enable Detailed Logging

Per-Call Logging

What Each Level Shows

Debugging Example

Logger Not Installed

Frequently Asked Questions

Q: Why are my annotations not found?

Q: How do I connect nodes between files?

Q: What if I don’t specify an output?

Q: Can I use putior in CI/CD?

Q: How do I track in-memory variables?

Q: Why does the diagram look different on GitHub vs locally?

Q: Can I use custom properties?

Q: How do I suppress validation warnings?

Getting Help

See Also

Label Loses Text After `<`

Title Shows `<` or Loses Text