Strange issue in N1QL Query's in Console

I have seen some strange things lately in the Web console when working on N1QL querys. When i for example run the below query

SELECT META().id AS DocId,
       Owners.ownerNameFormatted AS fo_fullname,
       PropertyAddress.houseNumber AS sano,
       PropertyAddress.streetName AS address,
       PropertyAddress.place_id AS place_id,
       PropertyAddress.latitude AS latitude,
       PropertyAddress.longitude AS longitude,
       PropertyAddress.location_type AS location_type,
       apn AS apn,
       SalesInfo.lastSaleDate AS sale_date,
       CASE WHEN Marketing.privacy = 1 THEN TRUE ELSE FALSE END privacy,
       tract AS tract,
       CASE WHEN ownerOccupied = 'O' THEN 'Owner' WHEN ownerOccupied = 'A' THEN 'Absent' ELSE 'Others' END AS oao
FROM Contacts c
WHERE _type = 'farm'
    AND tract IN ARRAY_FLATTEN((
    SELECT RAW d.tract_id
    FROM Contacts d USE KEYS "tract_info::B063A42D-6C90-4060-95E6-0BAC11804767"),
1)
AND PropertyAddress.streetName = "Agia"
AND Marketing.privacy = 1 ORDER BY TO_NUMBER(PropertyAddress.houseNumber)

I get a valid result as expected but then in the query window i see a bunch of undefined which seems to always happen in the where portion of the query

WHERE _type = 'farm'
    AND tract IN ARRAY_FLATTEN((
    SELECT RAW d.tract_id
    FROM Contacts d USE KEYS "tract_info::B063A42D-6C90-4060-95E6-0BAC11804767"),
1) undefined
undefined    AND PropertyAddress.streetName = "Agia" undefined
undefined    AND Marketing.privacy = 1 undefinedORDER BY TO_NUMBER(PropertyAddress.houseNumber)

What causes this and how can i get rid off it ?

Hi @aponnath, you may have run into a bug in the query formatter. Which version are you running? There is an option in the settings dialog for the query workbench that controls whether formatting is automatically done. If you turn that off, it should prevent the problem from occurring.

-Eben

Thanks, yes upgrading to the latest version eliminated that bug