Bug: Maps can't be defined with variable keys

[JacksonBowe]

Trying to write the most basic of basic TBEL scripts. It's the most painful programming language I've ever experienced.

Can't wrap my head around the below behavior for example:

// Doesn't work
var x = 'hello';
var mapAdd = { x: 'hi' };
// Output: { "x": "hi" }

    
// Works
var x = 'hello';
var mapAdd = {};
mapAdd.put(x, 'hi');
// Output: { "hello": "hi" }

[ilyar]

I looked at this because the reported behavior is easy to reproduce, but there is an important compatibility concern.

TBEL already appears to treat bare keys in object/map literals as string keys. For example, patterns like {msg: newMsg} are used to produce a map with the literal key "msg". Changing {x: "hi"} to evaluate x as a variable would likely break existing scripts that rely on literal bare keys.

Would a separate computed-key syntax be acceptable instead, for example something like {(x): "hi"} to mean “evaluate x and use its value as the key”, while keeping {x: "hi"} as the current literal-key behavior?

If that direction is acceptable, I can prepare a small PR with regression tests covering both behaviors.

[JacksonBowe]

@ilyar It's not much concern to me at this stage as I've already written the script. Perhaps even a note in the documentation would work?

The main problem I had is that it's really hard to test the outputs of scripts inside Thingsboard. For my case I was using the output window as a janky form of console.log(). This already makes it hard to verify code, without the additional layer of TBEL not behaving in a way I'd expect.