Issue on the Model after creation of a Client according to RAML Definition

[stselo]

After install of RAML Tools for .NET, I created a model for the client of a Mule Application based on its RAML specifications. The point is that the model of Messages for the Request is not aligned with the specifications. To be more specific, the class of Request that was created does contain the properties for direction, interface_id and legacy_system but it does not include the property for keys which is also defined.

May I ask if you have any idea why the property of Keys is not included in Request Class? Is there any bug on the Tool side or it could be related with a format problem on the RAML file that makes the tool to ignore the Keys property in the context of Request?

Definition of request Type

Definition of request-line Type

The relative classes that created automatically by the “RAML Tools for .NET” after the use of the RAML file containing the above definitions for the request and key data types are as follows. Definition of Request Class after import of RAML File

Definition of Keys Class after import of RAML File

Please find below Version Information • Target framework is .NET Core 3.1 • RAML.NetCore.APICore package version is 0.2.0 • Microsoft.AspNet.WebApi.Client package version is 5.2.6 • RAML Tools for .NET downloaded from this link https://marketplace.visualstudio.com/items?itemName=MuleSoftInc.RAMLToolsforNET

[trycatchdonothing]

I have a similar issue. Seems like any nested objects that can't be resolved are just ignored in the generated CS output file. Did you find a fix for this?