Error message with dot access can be very confusing.

[evinism]

If you index a string using dot access, you get a very confusing error message stating that we expected a number, but got a string. This does not lead to a good debugging experience. Comes from this SO post. This is also likely an issue with all invalid dot accesses in MistQL.

Example

Data: "{\"foo\": \"bar\"}"

Query: @.foo

Expected: Error stating that dot access on strings is not allowed.

Actual: MistQLTypeError: Expected RuntimeValueType.Number, got RuntimeValueType.String