Mixin Inspector

A VS Code / Cursor extension that helps you read, understand, and safely edit JATE mixin configurations without leaving your editor.

Why it exists

Editing JATE config files (mixins, handlers, routes) is powerful but easy to get wrong. Today the usual loop is:

1. Change a mixin.
2. Re-run JATE.
3. Look at the output to see what actually changed.
4. Repeat.

Mixin Inspector removes that loop. It resolves mixins the same way JATE does, right inside the editor, so you can:

• See the fully resolved configuration as you type, without re-running JATE.
• Spot unwanted changes immediately, before they ship.
• Understand where a mixin is used and how it is composed across brands and partners.

The goal is simple: make editing JATE configs faster and less error-prone.

Features

1. Usage counts inline (CodeLens)

Every mixin definition and reference shows a small N usages label right above it. Click it to jump straight to every place that mixin is consumed.

No more guessing whether a mixin is safe to change — you can see its blast radius at a glance.

2. Show Usages (peek view)

Run Mixin Inspector: Show Usages (or click the N usages lens) to open an inline peek listing every usage across all partners and config files. Navigate them without losing your place in the current file.

3. Resolution Tree

Run Mixin Inspector: Show Resolution Path (or click the resolution tree lens) to open the Mixin Resolution Tree panel. It shows how a mixin is built up — which handlers and other mixins extend it, and in what order.

The tree flags problems automatically:

• ⚠️ circular reference — a mixin that ends up extending itself.
• ❌ not found — a reference that points to a mixin that does not exist.
• 🔁 already shown above — a duplicate branch, collapsed to keep the tree readable.

Click any node to jump to its exact source location.

The tree also surfaces problems like circular references so you can catch them before they ship:

4. Resolved Body preview

Inside the resolution tree, expand any node to see its resolved body — the final JSON after all extends, variables, and layers are applied. Click it to open the full resolved JSON side-by-side with your file.

This is the "what will JATE actually produce?" view — without running JATE.

5. Find All References

Native Find All References (right-click → Find All References, or Shift+F12) works on any mixin, so it feels just like navigating regular code.

6. Always up to date

The extension watches your config files and refreshes automatically as you edit. You can also force a rebuild with Mixin Inspector: Refresh Index.

Getting started

1. Open your JATE workspace.
2. The extension activates automatically when it detects a conf/routes folder.
3. Open any config JSON file — you'll see usage counts and lenses appear on mixins.

That's it. No setup required for the default project layout.

Settings

Commands

Open the Command Palette (Ctrl+Shift+P / Cmd+Shift+P) and search for "Mixin Inspector":

Tips

• Put your cursor on a mixin name and run a command directly — no need to select the text.
• Use the resolution tree while editing to confirm a change resolves the way you expect before committing.
• Watch the usage counts: a sudden change in the number is a quick signal that an edit affected more than you intended.