Code Template Framework: Attribute Constraints

[Uffe]

Hi!


The Code Template Framework allows access to Class constraints only, but Attributes, Connectors and Packages can all have constraints too.

I suggest the following:

• Rename the macros constraint* -> classConstraint*
• Add attConstraint*
• Add connectorConstraint*
• Add packageConstraint*
• Remove connectorSourceConstraint and connectorDestConstraint (connectorSourceElem* and connectorDestElem* should take care of those)

To me personally, the attConstraint* ones are the highest priority.

Cheers,


/Uffe

[«Midnight»]

[edit]Changes with emphasis added in response to Frank's point.[/edit]

I agree, with the exception of the priority ranking. IMHO they are all equally important. Nor do I see this as an all-or-nothing scenario. The 'nothing' option is just plain unworkable, and since we can access class constraints we're beyond that point now.

IMHO this is a bug. It could be interpreted as a side effect of how EA implements items such as constraints and attributes; such a side effect is still a flaw. We have seen similar wrinkles in how (for example) tagged values are handled differently for elements, connectors, attributes and such. But in the case of tagged values we can usually get at the various objects and collections. We need access in the case of all constraint types as well. There are a few exceptions; these are clearly bugs in how the paradigm is implemented.

[Frank Horn]

But in the case of tagged values we can get at the various objects and collections.

Can we? What about tagged values on parameters?

[twilliamson32]

I concur with this request!