hasura / hasura/graphql-engine

Does all json path work? wild card in json path

Open
#6,816 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
32.1k
Forks
3k
PR merge metrics
PR metrics pending

Description

https://github.com/json-path/JsonPath#path-examples

| JsonPath (click link to try)| Result |
| :------- | :----- |
| $.store.book[*].author| The authors of all books |

When I have a jsonb column and tried this json path `$.interactions[*].source` in hasura query,

got an error:

```json
{
"errors": [
{
"extensions": {
"path": "$.selectionSet.xxxxxxxxxxx",
"code": "parse-failed"
},
"message": "parse json path error: $.interactions[*].source. Accept letters,
digits, underscore (_) or hyphen (-) only. Use single quotes enclosed
in bracket (['...']) if there is any special character"
}
]
}
```

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the Hasura query against a jsonb column with `$.interactions[*].source`, then trace the JSON path parser that reports the error. Confirm whether wildcard paths are intended to work and define done as either accepting this path correctly or documenting the supported syntax and limitation.

Written by the indexing model from the issue text.

Assessment

Tech stack
graphql, postgresql
Domain
api, databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
18/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.