Squidex API’s get call not working when code generated via NSWAG

Manjeera_Reddy · March 12, 2021, 1:22am

I have…

[ ] Read the following guideline: https://docs.squidex.io/01-getting-started/installation/troubleshooting-and-support. I understand that my support request might get deleted if I do not follow the guideline.

I’m submitting a…

[ ] Regression (a behavior that stopped working in a new release)
[ ] Bug report
[ ] Performance issue
[ ] Documentation issue or request

Current behavior

Hi Sebastian,
We are generating RestSharp Client via NSWAG. We are getting error when we call Squidex API from the code generated via NSWAG for GET methods. We see “iv” property is removed which is causing the issue .

Expected behavior

Minimal reproduction of the problem

Environment

[ ] Self hosted with docker
[ ] Self hosted with IIS
[ ] Self hosted with other version
[ X] Cloud version

Version: [VERSION]

Browser:

[X ] Chrome (desktop)
[ ] Chrome (Android)
[ ] Chrome (iOS)
[ ] Firefox
[ ] Safari (desktop)
[ ] Safari (iOS)
[ ] IE
[ ] Edge

Others:

Sebastian · March 12, 2021, 2:00pm

Hi,

what do you mean with “iv” is removed? I made an improvement and use a “map” now for properties so that the code generators create Dictionaries or HashMaps or objects for all fields.

Manjeera_Reddy · March 14, 2021, 6:31am

Hi Sebastian,
We generated RestClientClient code NSWAG and we are getting build errors. Also earlier we used to see “Iv” property under the field. But now we see fields of type Dictionary object which is giving build errors when we have ICollection.

Could you please take a look.

Thanks,
Manjeera T

Sebastian · March 14, 2021, 10:36am

Sure, I actually did the same and tested some builds with Nswag and made adjustments until the output looked as clean as possible.

Sebastian · March 14, 2021, 2:03pm

There are two things:

The breaking change that I have introduced and that should have been announced. Sorry for that.
The problem that NSwag has. You can fix it with the following settings: