Closed elisabettai closed 1 year ago
@odeimaiz, is it something that be easily fixed or do we need backend intervention?
What @mguidon reported is pure backend. Regarding what I see in the animation, I would need to have look.
@elisabettai @mguidon @odeimaiz there is a way around to this problem by using "pure-strings" enums on your schema. For instance, in this case modify the json-schema such that it ads a type
:
{
"title": "Solution method",
"description": "An enumeration",
"enum": [ "Iterative (GMRES)", "FMM-LU"],
"type": "string" # <-- NOTE THIS
}
This is legal in json-schema and you are basically saying that the values of the enum can only be strings. For more insight on the enum schemas you can look at https://github.com/pcrespov/sandbox-python/blob/98fb613a41e9c6a5a54f52be321cb652bfe047da/json-schemas/test_schemas_with_enums.py
This works like a charm! Thanks.
Initially reported by @guidon:
And also @elisabettai found the same while developing a new comp. service locally (see animation below)
When an enum is added in the input port schema, it breaks input matching for files. This is the error I see in the webserver:
Just for reference, this is the metadata.yml of the service: