Query syntax in blueprints ignores nested config variable when key contains a number

[TimOetting]

Describe the bug
From within my blueprint I would like to access a variable from a config array for a label. This does not work, if the array key contains a number. It then simply shows nothing as a label.

To Reproduce
Given the following config.php:

return [
    'places' => [
        "place1" => [
            'name' => 'Place 1'
        ],
        "placeTwo" => [
            'name' => 'Place 2'
        ]
    ]
]

the blueprint

title: My Places
fields:
  text:
    type: text
    label: "{{kirby.option("places").place1.name}}"

does not show anything as a label.

label: "{{kirby.option("places").placeTwo.name}}", however, would work.

Kirby Version
3.3.4

[afbora]

I can reproduce the issue, i'll track down. As workaround, you can use option key directly like that:

kirby.option("places.place1.name")

[afbora]

I found the issue. The query parts doesn't support any numbers. We need to ask @distantnative who refactor the code why doesn't support it. Btw works great when implemented as a-zA-Z0-9.

Related Query Class
https://github.com/getkirby/kirby/blob/3.3.4/src/Toolkit/Query.php#L18

[distantnative]

Maybe I just didn't imagine numbers as part of it....
Could be an easy fix as @afbora suggested. We would nee to run some tests.

[bastianallgeier]

✅