Closed jfantunes closed 6 years ago
webapiclientgen has limited supports for generic types like IList<> and IDictionary<> etc., however, supporting generics overall will require significant changes however it seems that using custom generic in Web API is not popular, since this is the first requirement after 3 years since webapiclientgen is released.
Let's see how many people would use custom generic?
@jfantunes , basically done. You may check out this repository and build then test with your .NET Core Web API project.
I had tested with ASP.NET Web API, .net client, jQuery and Angular2+.
If you find things are OK, I will be making a release.
Hi @zijianhuang, i've tested and works great. Thank you for your time. I'm sure many people would appreciate it, since sometimes generics are the best way to have less Dto's without the same information.
released webapiclientgen 2.5.0 and webapiclientgen 2.5.1. tested in https://github.com/zijianhuang/DemoCoreWeb and https://github.com/zijianhuang/webapiclientgenexamples
Hi! I have several classes that are generic. One of this is the following one:
For what im observing webapicodegen doesnt like it. When i pass the cherrypick option 1 or 8, he throws me an error 'System.ArgumentNullException: 'Value cannot be null.' Since has you stated before this is simillar to a template it's not a typed class, what can i make it to be more friendly to the codegen witout having major changes on code? Thanks.