jmespath / jmespath/jmespath.site

Tutorial: list vs array

Open
#113 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Makefile
Stars
61
Forks
61
PR merge metrics
No merged PRs in 30d

Description

It's not clear to me whether "list" and "array" are intended to have different meanings in the tutorial.

I could imagine that "array" would refer to the actual json datatype, while "list" would be a more general sequence of values. But the description of index expressions and slices use "array" consistently, implying these can only apply to arrays and not lists in general. That doesn't seem desirable.

This pair of sentences suggests that lists and arrays are equivalent
> A list projection is only valid for a JSON array. If the value is not a list, then the result of the expression is null.

If lists are a superset of arrays, then this leaves the behaviour of a list projection undefined if the value is a non-array list.

This sentence is also confusing if the index operator can only operate on an array, not a list:
> What if you wanted the first element in that list?

If "list" and "array" are intended to be different, some explanation of the difference would be helpful. If they are intended to be the same, I suggest using the JSON term "array" as much as possible. (And this is coming from a pythonista!)

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.