String variable value serialization is inconsistent

[barinali]

Describe the Bug

Cf.
bpmn-io/variable-outline#24 (review)
bpmn-io/variable-outline#24 (comment)

The diagram to observe this issue

String variables seems resolved in an inconsistent way. While a FEEL expressions output mapping variable such as ="No receipt attached" is resolved as below

{
  "name": "rejectionReason",
  "provider": [
    null
  ],
  "type": "String",
  "info": "No Receipt attached",
  "entries": [ ],
  "detail": "String"
}

exampleOutputJson's string property is resolved as below.

{
    "name": "rejectionReason",
    "type": "String",
    "info": "\"someString\"",
    "detail": "String"
}

Steps to Reproduce

1. Open this diagram
2. Focus on "Review report - manager"
3. Inspect rejectionReason variable in both root and local scopes
4. While local variable value has the quotations serialized, the root scope variable does not have them serialized

Expected Behavior

Consistency expected. It's either we need to serialize quotations for both or none.

Environment

• Library version: 2.0.0

[barinali]

@nikku created this issue as a follow-up on this remark. It seems we have some differences in serializations for values resolved as string.

[nikku]

From my (user) point of view: I'd like to

• see variables represented in a uniform way (string always represented in one way)
• distinguish variable types

As "hello world" is the canonical way to represent a string in FEEL, I'd expect that whatever is a string is represented "IN TICKS".

[barinali]

I have created #94 to make sure we are on the same page for what's expected. Regardless of FEEL or non-FEEL variables, the strings are in quotations based on the following remark.

see variables represented in a uniform way (string always represented in one way)