No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
One weakness | One weakness we recently rectified was the lack of enumeration definitions inside Modlr. Before, you had to assign an Enumerable type name to an attribute like so: | ||
[[File:Enumerations -1.png|frameless|213x213px]] | [[File:Enumerations -1.png|frameless|213x213px]] | ||
Line 7: | Line 7: | ||
[[File:Enumerations -2 .png|frameless|456x456px]] | [[File:Enumerations -2 .png|frameless|456x456px]] | ||
This was | This was simply because the Model was not informed about the Enumeration. In fact, you had to define the enumeration some place in the code yourself to get the CodeGen to use it. | ||
But | But now, you can get up this dialog (add model elements, Edit Enumerations): | ||
[[File:Enumerations -3.png|frameless|476x476px]] | [[File:Enumerations -3.png|frameless|476x476px]] | ||
Here, you declare the enumeration name, values, and code comments (and also the optional integer value). | |||
If the CodeGen checkbox is checked we will add the enumeration to your code. The important thing here is that the model has been made more detailed by keeping the knowledge about enumerations inside the model | If the CodeGen checkbox is checked, we will add the enumeration to your code. The important thing here is that the model has been made more detailed by keeping the knowledge about enumerations inside the model so that we can use the enumeration values in constraints, ViewModel validations, etc. | ||
[[Category:MDriven Designer]] | [[Category:MDriven Designer]] | ||
[[Category:OCL]] | [[Category:OCL]] |
Revision as of 07:49, 28 February 2023
One weakness we recently rectified was the lack of enumeration definitions inside Modlr. Before, you had to assign an Enumerable type name to an attribute like so:
And then accept that Modlr treated your attribute of type string and not as an Enumerable:
This was simply because the Model was not informed about the Enumeration. In fact, you had to define the enumeration some place in the code yourself to get the CodeGen to use it.
But now, you can get up this dialog (add model elements, Edit Enumerations):
Here, you declare the enumeration name, values, and code comments (and also the optional integer value).
If the CodeGen checkbox is checked, we will add the enumeration to your code. The important thing here is that the model has been made more detailed by keeping the knowledge about enumerations inside the model so that we can use the enumeration values in constraints, ViewModel validations, etc.