Change
Remove uses of TopicProxy from constraints package
Issue description
A topic proxy consists of label and type. The label is computed and might use the label rules which need the Tobject API which needs the constraints. Therefor it is better to avoid the use of TopicProxy in the constraints package.
Developer comments
All uses have been removed, except for one which is used by the client as well. It could be an option to simply augment that property later in the related resources .form and .constraints.
With [13515, the bug] fixed, accepting the remaining use of TopicProxy in the constraints package seems to be the better choice currently, since with the same reasoning all uses of Label::get would need to be removed as well, since they also would eventually (under special conditions) use the API if the label is newly generated and label rules are evaluated. It would be neat to separate the technical core necessary to power the API of a topic type from its more decorative traits like its label. Only a very limted subset of all properties are necessary to acutally drive the API, but this is [13519, another issue].
|
|
We are sorry
This page cannot be displayed in your browser. Use Firefox, Opera, Safari, or Chrome instead.