Variables: Inconsistency in multi value variable interpolation + custom format

[yesoreyeram]

This issue is nothing to to do with the new sub property variable. This issue is just to highlight the inconsistency when handling multi value variable. As you can see in the below screenshot,

• values of ${users} joined with ,
• values of ${users:text} joined with +
• values of ${users:value} joined with {,}

similar inconsistency followed when used with doublequote or any other custom formatter.

Dashboard JSON

{
  "annotations": {
    "list": [
      {
        "builtIn": 1,
        "datasource": {
          "type": "grafana",
          "uid": "-- Grafana --"
        },
        "enable": true,
        "hide": true,
        "iconColor": "rgba(0, 211, 255, 1)",
        "name": "Annotations & Alerts",
        "type": "dashboard"
      }
    ]
  },
  "editable": true,
  "fiscalYearStartMonth": 0,
  "graphTooltip": 0,
  "links": [],
  "panels": [
    {
      "fieldConfig": {
        "defaults": {},
        "overrides": []
      },
      "gridPos": {
        "h": 8,
        "w": 12,
        "x": 0,
        "y": 0
      },
      "id": 1,
      "options": {
        "code": {
          "language": "plaintext",
          "showLineNumbers": false,
          "showMiniMap": false
        },
        "content": "| Template  | Interpolated Value |\n|-----------|--------------------|\n| $\\{users} | ${users} |\n| $\\{users:text} | ${users:text} |\n| $\\{users:value} | ${users:value} |\n| $\\{users:doublequote} | ${users:doublequote} |\n| $\\{users:text:doublequote} | ${users:text:doublequote} |\n| $\\{users:value:doublequote} | ${users:value:doublequote} |\n",
        "mode": "markdown"
      },
      "pluginVersion": "12.4.0-20299387718.patch2",
      "title": "",
      "type": "text"
    }
  ],
  "preload": false,
  "schemaVersion": 42,
  "tags": [],
  "templating": {
    "list": [
      {
        "allowCustomValue": false,
        "current": {
          "text": [
            "foo",
            "bar"
          ],
          "value": [
            "foo",
            "bar"
          ]
        },
        "multi": true,
        "name": "users",
        "options": [],
        "query": "Mr.Foo : foo, Mrs.Bar : bar",
        "type": "custom"
      }
    ]
  },
  "time": {
    "from": "now-6h",
    "to": "now"
  },
  "timepicker": {},
  "timezone": "utc",
  "title": "New dashboard",
  "version": 0,
  "weekStart": ""
}

Details

[grafakus]

Not sure to understand what the bug is. Can you provide:

1. a minimum scenario that can be reproduced locally
2. the current output
3. the expected output
   ?

Thank you!

The dashboard you shared from Grafana Play uses under the hood the Infinity data source. Does this data source support variable object values with multiple properties? Does it creates MetricFindValue[] or does it pass the data frames to Scenes?

EDIT: Now looking at your draft PR, it seems it's currently not supporting multiple properties 🤔 I'm a bit confused. Can you shed some light? Thanks!

[yesoreyeram]

@grafakus - Sorry for the confusion and missing / irrelevant details. This issue is nothing to to do with the new sub property variable. This issue is just to highlight the inconsistency when handling multi value variable. Updated the issue description.

[grafakus]

Ok, got it. Can we also move the conversation from grafana/grafana#113844 (comment) to here?

Because it's not related to my PR in core Grafana, it'll help keep the conversation focused. Thank you!