In the Concerto model below the field Zoo.animals can contain any type that extends the abstract type Animal. Concerto-UI does not allow the user to select the type that they want to add to the array - it appears to pick the first non-abstract type.
It would be great if (when there is more than 1 abstract type that extends a base type) the UI allows the user to explicitly select the type (both for array and for non-arrays).
namespace acme
abstract concept Animal {
o String name
}
concept Tiger extends Animal {
}
concept Lizard extends Animal {
}
concept Zoo {
o Animal[] animals
}
Feature Request 🛍️
In the Concerto model below the field
Zoo.animals
can contain any type that extends the abstract typeAnimal
. Concerto-UI does not allow the user to select the type that they want to add to the array - it appears to pick the first non-abstract type.It would be great if (when there is more than 1 abstract type that extends a base type) the UI allows the user to explicitly select the type (both for array and for non-arrays).
Here is the JSON created by Concerto-UI:
Use Case
Editing of Concerto model instances that contain a type hierarchy.
Possible Solution
Note that the sample generation code in Concerto already includes some logic to pick non-abstract types.