[csharp,java] Generated output includes Object.cs which produce compile error an 'Object' is an ambiguous reference

Both v 2.1.5 and todays master (8 feb 2016) generates - for my project - a dummy Object file with no properties that gives compile errors unless it is deleted. Problem applies to both Java and CSharp version but below I will focus on the CSharp error. The does not happen with all projects (as an example, petstore works fine) but it happens with mine that was generated by Ahoy/swashbuckle. See attached file test-swagger_json.txt

For CSharp the generated dummy model is called Object and placed in an Object.cs file (see attachment below). It is not used and when removed the project will compile. So the problem seems to be that the file is generated at all.

Object.txt

[wing328]

The endpoint ApiServicebureauByServicebureauIdEmployeersByEmployeerIdEmployeesByEmployeeIdPatch has body parameter referring '#/definitions/Object', which seems not defined (which means it's an object without property)

Yes, that could be why. Patch operations typically takes opaque input (which Ahoy/swashbuckle translates into Object for Java and C#). No Object file should be generate though as it refers to java.lang.Object (java) or System.Object (c#). The question is if the problem is in Ahoy/swashbuckle that fails the prefix the package/namespace to Object OR if the problem is in swagger-codegen that fails to filter out references to build-in system classes like Object ?

[wing328]

I don't think #/definitions/Object translates to Object (in C#, Java or other langauges). It means a model named "Object" defined under definitions.

What does the body parameter look like? What about defining the body parameter as a proper model (with properties) as opposed to just a generic object?

In C# the type is a "dynamic" which is a type that can contain anything and be inspected at runtime for actual content. The corresponding method (ASP.NET 5 / MVC 6) is

public IActionResult MergeEmployee(uint servicebureauId, uint employeerId, uint employeeId, [FromBody]dynamic employeeChanges)

[wing328]

Ideally you want to be able to supply any object but the question is how can these objects be serialized properly into JSON string (to be placed in the HTTP body)?

What does the HTTP body look like?

UPDATE: fix typo.

The HTTP body contains arbitrary json. The newtonsoft library which is used for serialization/deserialization can deserialize any json into a "dynamic". At runtime I can ask the dynamic type what properties it has etc. This is pretty nice for patch operations, since patch objects are not complete objects so I can't make a static type for the input.

[wing328]

Thanks for sharing the requirement but that's not supported at the moment.

That is ok. I can work around it for now by deleting the file after generation or by adding "--import-mappings Object=System.Object"

[jimschubert]

I've actually encountered this in C# by returning an anonymous object. For me, I think it's a result of Swashbuckle generating certain swagger definitions. If I remember correctly, I resolved the issue by creating a view model and annotating with the response:

[SwaggerResponse(HttpStatusCode.OK, Type=typeof(MyViewModel))]

I think a quick hacky fix would be to check returnType in the generator and if it's Object (and not System.Object), change it to modelPackage + ".Object". There could be a cli parameter to allow System.Object return types that doesn't do this fix.

[wing328]

@bluemmc @jimschubert I've made some improvement via #2317. Would you please pull the latest master and give it another try?