hasura / hasura/graphql-engine

Kriti "range" does not work in request options transform

Open
#9,196 3 comments 0 reactions 0 assignees View on GitHub
k/enhancement
Dominant language
TypeScript
Stars
32.1k
Forks
3k
PR merge metrics
PR metrics pending

Description

### Version Information

Server Version: 2.12.0

### What is the current behaviour?

> Parse Error: Unexpected token 'range'.

### What is the expected behaviour?

Range works as documented so you can perform array transforms: https://hasura.io/docs/latest/api-reference/kriti-templating/#control-flow

### How to reproduce the issue?

![image](https://user-images.githubusercontent.com/13342266/200716883-2848350d-0b05-4ec5-84d3-632b3a511813.png)

### Please provide any traces or logs that could help here.

### Any possible solutions/workarounds you're aware of?

### Keywords

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the parse error in the request options transform using the issue's Kriti range example, then compare it with the linked control-flow documentation. Trace the Kriti parser or grammar entry point for request transforms; done means range parses and performs the documented array transform.

Written by the indexing model from the issue text.

Assessment

Domain
api
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.