Constrained string types translate to a PrimitiveType without further info

[woppa684]

The TypeScript implementation tries to decode this as a builtin type, but throws an error. It would be probably be best to just interpret such a type as a normal string for now.

{
    "children": [
    ],
    "concept": {
        "key": "PrimitiveType",
        "language": "LIonCore-M3",
        "version": "1"
    },
    "id": "NWQ4ZDZmZTUtODExZS00NTBhLWFhYjEtZjA2YzBkOWJhODk2LzU3NjkwMjQ5ODM1NjA4NjAxNzU",
    "parent": "NWQ4ZDZmZTUtODExZS00NTBhLWFhYjEtZjA2YzBkOWJhODk2",
    "properties": [
        {
            "property": {
                "key": "IKeyed-key",
                "language": "LIonCore-M3",
                "version": "1"
            },
            "value": "NWQ4ZDZmZTUtODExZS00NTBhLWFhYjEtZjA2YzBkOWJhODk2LzU3NjkwMjQ5ODM1NjA4NjAxNzU"
        },
        {
            "property": {
                "key": "LIonCore-builtins-INamed-name",
                "language": "LIonCore-builtins",
                "version": "1"
            },
            "value": null
        }
    ],
    "references": [
    ]
}

[enikao]

Does this relate to the MPS implementation or TypeScript? If the latter, please open a bug in https://github.com/LIonWeb-org/lioncore-typescript

[woppa684]

Not really I guess. It is not wise to map all non-builtin PrimiteTypes to string. On the MPS side you at least know that something is a constained string type, so it would be better to map that to string there.

[enikao]

Ok, now I get it. I've never seen a constrained string type in the wild, that's why I didn't think about it.