#2615 PDS3 completions show where variable must be manually included in label

[Jeremy Faden]

Completions for PDS3 didn't have the variable name in the completion label, making it very confusing when you knew what the variable name was but not how to type it. The code making labels for each completion should add the completion ("EPOCH") to the label ("EPOCH: the timetags").

[Jeremy Faden]

This was just just before v2024a_7 was released, but I just found a case where the label is poor.

1. plot demo 2
2. add "&" after 20000109, and trigger completions

Labels like "20000109&where=" are shown.

This is fixed.

[Jeremy Faden]

Here's a case which is now broken:

vap+hapi:https://wdcapi.bgs.ac.uk/hapi?id=cax/PT1M/xyz&parameters=Time,Field_Vector&timerange=2020-01-01

and then completions after 'cax/'. Each entry has the time in the label: "2020-01-01: cax/PT1M/xyz"

[Jeremy Faden]

JADE PDS3 completions, too.

[Jeremy Faden]

This is fixed for these two cases.

[Jeremy Faden]

I notice completions in scripts are oddly missing the variable name. Reopening ticket...

[Jeremy Faden]

I ran into this again. It's clear what is wrong if I compare completions of the same URI in the address bar vs completions within a script. Also I notice "huh." is printed on stdout, as if there was code which was not completed.

[Jeremy Faden]

I cleaned things up so they look right in the automatically generated GUI, but I suspect that this breaks other places. Completions must work:

• [x] in the automatic GUI
• [x] when completing in the address bar
• [ ] when completing in scripts

[Jeremy Faden]

It still fails when completing within scripts: