KXI-58865 - [structuredText] char result renders incorrectly

[Philip-Carneiro-KX]

Changes introduced by this PR

• fix char type wrapper bug for local q

[acheung12]

Why do you need this addition? Scratchpad does not have this. Keep in mind scratchpad toStructuredText also does goes through the sampling function before being called however whose return value will be used for toStructuredText and is accurate.

[ecmel]

@acheung12 This should be fixed in Insights scratchpad as well. (https://kxl.atlassian.net/browse/KXI-58865) since evaulate.q and Insights returns the same response for the specific query.

[acheung12]

@acheung12 This should be fixed in Insights scratchpad as well. (https://kxl.atlassian.net/browse/KXI-58865) since evaulate.q and Insights returns the same response for the specific query.

Scratchpad handles the raw response which looks correct to me. The results view is UI?

[ecmel]

Insights scratchpad returns the following for structuredText:

data ='{"count":4,"columns":{"name":"values","type":"chars","values":["\\"Done\\""],"order":[0]}}'

It has only 1 value in array but count is 4. If this is correct, we should refactor extension code.

[acheung12]

@ecmel This is correct. Strings in Q are considered to be char vectors. Therefore, the count is "done" is 4 AKA 4 characters. I'll bring this up to someone on Magenta if you wish for a redesign but I believe this is correct.

Below is a unit test that tests for the count and tostructText feature on scratchpad. This is considered correct.

[kx-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube