tiagobento commented on issue #1020: URL: https://github.com/apache/incubator-kie-issues/issues/1020#issuecomment-2015702586
As we discussed today between @ljmotta @gitgabrio @yesamer, we think the best course of action right now is: 1. For non-collection, we read constraints from `allowedValues` and `typeConstraints`, defaulting to `typeConstraints` if both are present. When writing, we always choose `typeConstraint`. 2. For collection types, we show two Constraints section. One for `allowedValues` and another for `typeConstraint`. In the future, if the `allowedValues` property is removed from the DMN spec, we can migrate models to extract a new type specific for the items of a collection type using `allowedValues`, and copying the `allowedValues` expression to its `typeConstraint` value. The `typeRef` of the collection type would refer to this new type. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
