fix: use scoped variables in the query builder

[maartenofzo]

When using repeated variables via the query builder, all multi-value variables were sent from each panel instead of using the scoped variables. This is the simple fix for that.

[simPod]

Can you please elaborate on what problem does this solve? Add a test so I can fully understand the change.

[maartenofzo]

Sure, this change makes sure that if you have repeating panels via multi-value variable that it uses the variable scope instead of sending all variables through json.

Example how it sends a scoped multi-value now:

{
  "targets": [
    {
      "datasource": { "type": "simpod-json-datasource", "uid": "qsUNIjEVz" },
      "editorMode": "builder",
      "payload": {
        "value1": "foo",
        "value2": "bar",
        "multi-value": "(foo|bar)",
      },
      "refId": "A",
      "target": "opsdata"
    }
  ],
  "scopedVars": {
    "value1": { "selected": false, "text": "foo", "value": "foo" },
    "value2": { "selected": false, "text": "bar", "value": "bar" },
    "multi-value": { "text": "bar", "value": "bar", "selected": true },
    "__interval": { "text": "500ms", "value": "500ms" },
    "__interval_ms": { "text": "500", "value": 500 }
  },
}

As you can see it sends (foo|bar) as if the multi-value was never scoped at all. In the scopedVars parameter you can see that the multi-value field actual has a scope where the value is only bar.

This code changes the payload so it only sends the scoped variable so it will look like this:

{
  "targets": [
    {
      "datasource": { "type": "simpod-json-datasource", "uid": "qsUNIjEVz" },
      "editorMode": "builder",
      "payload": {
        "value1": "foo",
        "value2": "bar",
        "multi-value": "bar",
      },
      "refId": "A",
      "target": "opsdata"
    }
  ],
  "scopedVars": {
    "value1": { "selected": false, "text": "foo", "value": "foo" },
    "value2": { "selected": false, "text": "bar", "value": "bar" },
    "multi-value": { "text": "bar", "value": "bar", "selected": true },
    "__interval": { "text": "500ms", "value": "500ms" },
    "__interval_ms": { "text": "500", "value": 500 }
  },
}

If no repeat setting is on, the variables will not be scoped, because scopedVars in that case is "undefined" already.

[simPod]

Overall, it makes sense.

But we need to adapt tests so it's not broken later. There's TemplateSrvStub you can use I think https://github.com/simPod/GrafanaJsonDatasource/blob/66da5e8b7365e959266c51d8536441d8fa8be93f/spec/lib/TemplateSrvStub.ts

I'll test this today on my G install.

[maartenofzo]

Wrote a test for it, used original variable types that Grafana uses. Let me know if this is alright.

[simPod]

Overall LGTM, the test documents the change sufficiently

[maartenofzo]

Updated based on your comments.

[simPod]

LGTM, let's try it. Thanks