Includes Markdown AST Metadata into non-code Cells

[pastuxso]

Metadata sample output:

{
  "Children": [
    {
      "Kind": "Text",
      "Text": "Paragraph 1 with a link "
    },
    {
      "Children": [
        {
          "Kind": "Text",
          "Text": "Link1"
        }
      ],
      "Destination": "https://example.com",
      "Kind": "Link",
      "Title": "Link Title 1"
    },
    {
      "Kind": "Text",
      "Text": " and a second link "
    },
    {
      "Children": [
        {
          "Kind": "Text",
          "Text": "Link2"
        }
      ],
      "Destination": "https://example2.com",
      "Kind": "Link",
      "Title": "Link Title 2"
    },
    {
      "Kind": "Text",
      "Text": ".."
    }
  ],
  "Kind": "Paragraph",
  "RawText": "Paragraph 1 with a link [Link1](https://example.com 'Link Title 1') and a second link [Link2](https://example2.com 'Link Title 2').."
}

[sourishkrout]

I'm undecided on using the runme.dev/ prefix for e.g. "runme.dev/3/Kind". We introduce it to pass additional information between extension <> kernel that's exempt from serialization. The metadata list is getting a bit busy using the same exact mechanism. Have you tried grouping the AST information under a single property, such as runme.dev/ast and just nest them @pastuxso?

[pastuxso]

@sourishkrout, I believe we could implement a nested structure, though it would necessitate significant modifications to our existing one. Alternatively, we could incorporate a stringified JSON under the key runme.dev/ast, allowing us to maintain the map[string]string format for metadata.

What do you think about the following structure?

{
  "runme.dev/ast": {
    "Kind": "Paragraph",
    "RawText": "Some content with [Link1](https://example1.com \"Link title 1\") [Link2](https://example2.com \"Link title2\")",
    "Children": [
      {
        "Kind": "Text",
        "Text": "Some content with "
      },
      {
        "Destination": "https://example1.com",
        "Kind": "Link",
        "Title": "Link title 1"
      },
      {
        "Kind": "Text",
        "Text": " "
      },
      {
        "Destination": "https://example2.com",
        "Kind": "Link",
        "Title": "Link title2"
      },
      {
        "Kind": "Text",
        "Text": "Link1"
      },
      {
        "Kind": "Text",
        "Text": "Link2"
      }
    ]
  }
}

[sourishkrout]

@pastuxso I like it better 👍 . Scopes/namespaces it under a single property.

[sourishkrout]

Let's figure out what's left to get this merged. We should probably just have a convo (after standup) or something about it.

[sourishkrout]

👍 LGTM. I saw some minor issues inside the AST info. However, let's merge for now and circle back later.