You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This tooling is awesome for generating types, but one thing I've noticed that its missing is the ability for it to generate an Interface for WebAPI Types.
As you likely know, when you go to retrieve records with the WebAPI, some of the attribute names you get back are slightly different. To give an example lookups have the format of _xxx_,myattribute_value... and each record gets an @odata.etag appended.
Also when you to to make updates, you have to use the capital sensitive [email protected] attribute.
So would it be possible to get the ability to generate API Types added in? I`m thinking it would mainly just be a variant of the IEntity Interface Types that are already being generated, but it would generate two entries for the Lookups. One for the API Retrieval Format, and one for the Create/Update format.
The text was updated successfully, but these errors were encountered:
Hey Scott, I've got a feature suggestion/request.
This tooling is awesome for generating types, but one thing I've noticed that its missing is the ability for it to generate an Interface for WebAPI Types.
As you likely know, when you go to retrieve records with the WebAPI, some of the attribute names you get back are slightly different. To give an example lookups have the format of
_xxx_,myattribute_value
... and each record gets an@odata.etag
appended.Also when you to to make updates, you have to use the capital sensitive
[email protected]
attribute.So would it be possible to get the ability to generate API Types added in? I`m thinking it would mainly just be a variant of the IEntity Interface Types that are already being generated, but it would generate two entries for the Lookups. One for the API Retrieval Format, and one for the Create/Update format.
The text was updated successfully, but these errors were encountered: