treat referenced type classes in the same way as composition association targets.

[onthebreeze]

refs #109 - please check out the classes like citizenship where some of the attributes have a type called "partialDate". You'll see that this type is defined in the Core Types package and it is essentially a little class with three attributes, day, month, year as separate properties. It is referenced as a type quite frequently throughout the applications api model. However the generator sees this as an unknown type and just replaces it with "string".

In general (and this will help with the CEFACT core types issue too) the generator should just follow these type definitions (whether generating from package or diagram) and should treat them is exactly the same way as a composition relationship - namely create a type for "partialDate" and reference it wherever it is used.

[onthebreeze]

Looks ok - I can see that the partialDate type now comes through

{
"jobTitle": "string",
"description": "string",
"startDate": [
{
"Day": "string",
"Month": "string",
"Year": "string"
}
],
"endDate": [
{
"Day": "string",
"Month": "string",
"Year": "string"
}
],
"employer": {
"name": "string",
"taxRegistrationId": "string"
}
}

[onthebreeze]

Reopening - there is a bug - the referenced type is shown as an array when it should be an object

So like this

"startDate":
{
"Day": "string",
"Month": "string",
"Year": "string"
},

Not like this

"startDate": [
{
"Day": "string",
"Month": "string",
"Year": "string"
}
],