Type descriptions in metaModel has types that are not in the metaModel

[karthiknadig]

No description provided.

[dbaeumer]

Can you point me to the places?

[karthiknadig]

Example:

"documentation": "Parameters for a {@link ColorPresentationRequest}."

The name: ColorPresentationRequest for a class that does not exist in the metaModel.

Probably, the request, notification, response, partial-result types should have names. This could make it easier to generate code for them, without trying to guess a name.

[dbaeumer]

The problem here is different. In TS the requests are namespace which they aren't in the meta model. We should rather in the documentation exchange them with the method name.

We could capture the namespace name. If we do so we need to ensure that it is clear that that name has no relevance for the implementation.