Make the meta-schema tab entries look more like a stack trace

[jviotti]

It seems to look like an independent sequence of problems to some. Their relationship is not obvious

[RitoG09]

I was able to reproduce the issue with metaschema failures where a single root error (e.g. invalid minimum type) propagates upward and results in multiple related metaschema errors.

From the raw CLI output, these errors clearly form a causal chain, but they are returned as a flat list, which makes the relationship hard to infer in the webview.

I wanted to know your preference on the approach:

• Should we consider enhancing the CLI (metaschema output) to encode this relationship more explicitly (stack trace like structure)?
• Or is the intent to keep the CLI output as it is and handle hierarchy purely at the extension level?

[jviotti]

@RitoG09 The idea is to fix it here in the extension. It's purely a visual thing. i.e. we should display the meta-schema tab in a way that better expresses that causal chain, and not as the same list widget we use for the linter.

But I'm not sure how that should look like. Open to suggestions :) How do other extensions or websites render stack traces? Maybe there is something to research there 🤔

[RitoG09]

I found 2 options suitable :

Option 1: Github Actions like logs->

Error: Validation failed
  └─ Caused by: Schema mismatch
       └─ Caused by: minimum expected number, got string

Option 2: Breadcrumb-style hierarchy->

@jviotti what do you think about these?

[jviotti]

I think the indentation approach, which I see on both, will not work for any meta-schema failure that goes a decent level of depthless. i.e. for some real custom meta-schemas, your stack trace might be like 50 entries, and thus the indentation or smaller font size won't really scale beyond 2 or 3.

What about we render on the left an arrow from one box to the other or something like that? i.e. quite literally showing the chain?

[RitoG09]

alright @jviotti will open a PR regarding this chain approach.