search

Autodesk-Forge / forge-api-dotnet-client

Forge .Net SDK: Provides .Net SDK to help you easily integrate Forge REST APIs into the application
https://www.nuget.org/packages/Autodesk.Forge/
Apache License 2.0
94 stars 70 forks source link

deserialization not implemented? #4

Open afshinjafari opened 7 years ago

afshinjafari commented 7 years ago

Hi, Although the documentation suggests to use classes as the outputs for API methods it seems it is not fully implemented: / Manifest / dynamic GetManifest (string urn, string acceptEncoding = null);

any time frame on when these are ready? thanks and regards, Afshin

cyrillef commented 7 years ago

Hi, Yes next version in about 2-3 weeks The reason I implemented dynamic vs the Manifest class is because the swagger-codegen parser which we are using to generate the code automatically from a yaml definition has bugs which I need to fix first.

afshinjafari commented 7 years ago

Hi, Thanks for the reply Cyrille, :) nice work as always, regards, Afshin

mace2000 commented 7 years ago

Hi What's the status of returning concrete classes instead of dynamic objects? Have you got any code samples how to convert data in DynamicDictionary to classes. Haven't got much experience with dynamic objects, but it seems rather a pain to turn a e.g. dynamic dictionary of projects into the Projects class.

bhosta commented 7 years ago

Hi, Any chance we could get an update on the status of this? or an example for deserializing the Manifest class?

autodesk-adn commented 7 years ago

Cyrille is on vacation this week, but I know this is on his list to do.

afshinjafari commented 7 years ago

Hi Cyrille, any update re this issue?

regards, Afshin

sdbrannum commented 4 years ago

Bumping this. Has or will there be any work done on this issue?