Accessing arrays with string keys: about jsonpath HOT 7 CLOSED

Yes it is intended. Values will be converted if they don't have the expected type.
This is also done in the base script language: https://github.com/PaesslerAG/gval

from jsonpath.

Hi @generikvault
Couldn't follow your answer regarding the string indices that are so because no expected value.
Can you elaborate on that and provide a sample?
Thanks.

from jsonpath.

Hi @moshevi

it's basically the example from above. If you have an array, let's say $.myarray, and access an element of the array via a string selector $.myarray["1"] the string will be converted to an integer.

This will not work for unsupported map types like map[int]interface{}.

from jsonpath.

Hi @generikvault
So why can't I use $.myarray[1] instead of $.myarray["1"] ?

from jsonpath.

$.myarray[1] works fine. The discussion was wether $.myarray["1"] should throw an array or convert the string to an integer.

Well and about the panic on negative indice but that is fixed.

from jsonpath.

Hi @generikvault
Sorry for misleading you....I meant that the returned paths from search expression (like: {#: $..[?(@.name == "Value")]} will be string indices and not numeric ones if the value is found inside an array.

from jsonpath.

Ah yes. Placeholder (#, #0, #1, ...) have a static string type and yeah this is something I'm not absolutly sure about.

from jsonpath.