Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Array/List values are not resolved as expected

Open
#82 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
52/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
backend

Research direction

Reproduce the issue by creating an input/output mapping with FEEL expressions and the value ["1", 1, { "test": { "sample": 123 } }]. Inspect the variable-resolver output against the expected List type, isList flag, and preserved entries; done means all values and nested schema are resolved without omissions.

Written by the indexing model from the issue text.

Description

backlog bug
Describe the Bug

Array/List values are not resolved as expected. Currently, a variable with a value of ["1", 1, { "test": { "sample": 123 } }] is resolved as below.

The problems I can observe;

  • type is Context, but should have been List
  • First two entries that are "1" and 1 are omitted, but should have been preserved and resolved accordingly
  • isList flag is missing
{
    "name": "arrayValue",
    "provider": [
        null
    ],
    "type": "Context",
    "info": "",
    "entries": [
        {
            "entries": [
                {
                    "atomicValue": 123,
                    "entries": [],
                    "type": "Number",
                    "info": "123",
                    "name": "sample",
                    "detail": "Number"
                }
            ],
            "type": "Context",
            "info": "",
            "name": "test",
            "detail": "Context"
        }
    ],
    "detail": "Context"
}
Steps to Reproduce
  1. Create an input/output mapping
  2. Enable FEEL expressions
  3. Provide a value like ["1", 1, { "test": { "sample": 123 } }]
Expected Behavior

variable-resolver resolves this variable with type=List and isList=true (?) and its entries accordingly without omitting sub-values and their schema.

Environment
  • Library version: main, cover-null-variable-type
Dominant language
JavaScript
Stars
0
Forks
1
Avg merge
8h 41m
Merged PRs (30d)
3

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from bpmn-io/variable-resolver

All issues in bpmn-io/variable-resolver

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.