influxdata / influxdata/chronograf
Chronograf 1.10.9 - Flux script editor inserts inline lambda functions as pipeline functions
- Dominant language
- TypeScript
- Stars
- 1.6k
- Forks
- 250
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 9
Description
__Steps to reproduce:__
List the minimal actions needed to reproduce the behavior.
1. Create a basic flux pipeline using pipeline builder
2. Open script editor
3. Add a `map` function.
4. Within the lamda function for the `map` pipeline function set the cursor to a location where an inline function like `strings.trimRight` is desired.
5. In the "Flux Functions" panel locate the `strings.trimRight` function.
6. Click to insert the function automatically into the lambda function.
The inline function is added as a pipeline function instead.
__Screencast__
https://github.com/user-attachments/assets/8f55db56-999b-4f64-aff6-54ef8bfbb241
__Expected behavior:__
Expected that the inline function would be inserted at the location of he cursor.
__Actual behavior:__
The inline function is inserted as a pipeline function.
After clicking "Run Script" an error occurs. "missing property value"
__Environment info:__
OS: Ubuntu 24.04
Browser: Opera 127
Backend: Influxdb1 OSS in docker.
Chronograf: 1.10.9
__Config:__
__Logs:__
```
INFO[7481] Response: Bad Request component=server method=POST remote_addr="[::1]:40810" response_time=11.813163ms status=400
INFO[7488] Response: OK component=server method=GET remote_addr="[::1]:46800" response_time="55.595µs" status=200
```
Contributor guide
Research direction
Reproduce the issue through the pipeline builder, script editor, and Flux Functions panel using a map lambda and strings.trimRight. Trace the function-insertion behavior at the cursor location and verify that the inline function is inserted inside the lambda rather than as a pipeline function. Done means the generated script runs without the “missing property value” error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100