You’re knee-deep in a Logic Apps run history at 2 a.m., wondering why your DotLiquid template turned a simple sales order into gibberish XML.
VS Code DotLiquid Debugger just landed like a caffeine IV drip. Shopify’s Liquid preview? Cute, but useless here—Logic Apps Standard chews DotLiquid, not that flavor. Behaviors clash. Templates ace the preview, flop in prod. And the default test loop? Update. Deploy. Wait. Squint at history. Repeat. For B2B data wrangling, that’s not development; it’s medieval torture.
This extension? It runs your .liquid files locally, wielding the exact same DotLiquid 2.0.361 engine as Azure. Same NuGet guts, same quirky integer division, same sentence-case filters. No simulations. No “close enough” lies. If it renders clean here, prod won’t bite—mostly.
Look. I’ve seen tools promise parity before. They don’t deliver. But this one’s a thin VS Code skin over a real .NET renderer. TypeScript front, DotLiquid backend via NDJSON pipes. First compile lags (fair), then? Sub-100ms renders. Keystroke to output. Bliss.
Why Logic Apps Liquid Debugging Was Pure Hell
Hit Ctrl+Shift+L on any .liquid file. Boom—preview panel. Auto-refreshes on save, or keystroke (debounced, thank god). No more cloud waits.
Paired input? Just drop a .liquid.json next door with test data. None exists? Banner nags you to make one. Smart.
But the killer: Debug button. Step-by-step replay. Assigns, loops, ifs—each gets spotlighted. Source line glows. Variables panel dumps state. Unassigned vars? Dimmed. Obvious what’s alive.
Slider scrubs steps. Prev/Next. Jump ends. Pinpoint why that var’s trash.
Filter chains? Glorious breakdown:
499.9 | Times:5 → 2499.5 | DividedBy:100 → 24.995 | Round:2 → 25.0
Math filters (Times, DividedBy, all that), strings (Upcase, Replace), arrays (Split, Map)—31 covered. Logic Apps? Zero visibility. This isolates chain fails instantly. Four-filter mess? See the divergence. No guesswork.
ifs? Conditions shown, green check if taken. Untaken branches? Skipped—mirrors DotLiquid exactly. Branches mystery solved.
Variables link to assign lines—click, jump. Output chunks map back to source. Click JSON “grandTotal”: 336.20—zap to the calc line. XML? JSON? Flat text? All good. No hacky debug spew needed.
Panels collapse, resize. Clean.
Does This Really Match Azure Logic Apps Production?
Short answer: Damn close.
This is the critical part: it uses the exact same engine — not a simulation. Not a compatible implementation. The same NuGet package, the same version, the same sentence-cased filters, the same content wrapping behaviour, the same integer division quirks.
That’s from the docs. Bold claim. But yeah—long-running .NET subprocess, compiled on-demand, NDJSON for concurrency. Handles Logic Apps’ four output flavors: flat JSON, XML, whatever.
Skeptical? Me too. Microsoft’s ecosystem loves gotchas—Shopify Liquid vs DotLiquid being exhibit A. But this sidesteps it. Local == prod engine. Fewer deploys. Less bill shock.
Here’s my hot take, unmentioned in the original: This echoes Node’s inspector era. Pre-2010s JS debugging? Console.logs and prayers. Then Inspector dropped—step-debugging bliss. Liquid devs lived in that stone age. This drags ‘em to 2024. Bold prediction: Expect Shopify migrants to Logic Apps spiking. Why fight cloud lag when local’s instant?
Corporate spin? None here—it’s open-ish, practical. Not hype. Rare win.
The Real Workflow Shift
Old way: Tweak template. Logic App run. 30s+ wait. History autopsy. Curse filters.
New: Edit .liquid. See render live. Debug step. Fix chain. Done.
B2B transforms—sales orders to invoices—thrive on this. Costly errors? Vanished.
Quirks? Warm-up compile. Mac Cmd+Shift+L. Minor.
Arrays? Loops shine—step each iteration, vars update live. No black box.
String mangling? Truncate gone wrong? Trace it.
Math bombs—Modulo surprises, Floor vs Round? Exposed.
Logic Apps users: Install now. VS Code marketplace, search “DotLiquid Debugger”. Free. Zero excuses.
But wait—does it catch everything? Nah. Runtime context quirks (custom filters? Nah), but 90% pains? Nailed.
And Logic Apps’ inline editor? Trash for complex templates. This? Pro.
Wander a bit: Reminds me of early Terraform debug hell. Tools like this mature ecosystems. Microsoft, take notes—bake it in.
Why Devs Ignore This at Their Peril
Bottleneck crushed.
Prod surprises slashed.
Debug hacks obsolete.
If you’re wrangling Logic Apps Liquid—stop suffering.
This isn’t fluff. It’s surgery on your workflow.
Dry humor aside: Finally, a tool that doesn’t make you want to hurl your laptop.
🧬 Related Insights
- Read more: Cloudflare’s Programmable Flow Protection: Customers Finally Script Their Own DDoS Defenses
- Read more: Kubernetes Devs Get Zero-Code LLM Observability — toil drops, costs plummet
Frequently Asked Questions
What is VS Code DotLiquid Debugger?
VS Code extension for local debugging of DotLiquid templates using Azure Logic Apps Standard’s exact engine. Instant previews, step-through debug.
How do I debug DotLiquid templates in VS Code?
Install extension, open .liquid file, Ctrl+Shift+L (Cmd on Mac). Add .liquid.json for data, hit Debug for steps.
Does DotLiquid Debugger work with Logic Apps?
Yes—matches DotLiquid 2.0.361 exactly. Filters, quirks, outputs align for fewer prod fails.
