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
{{ message }}
This repository has been archived by the owner on Jul 14, 2023. It is now read-only.
One way to specify the EDM type of a property is by providing an additional propertyName + "@odata.type" value which tells the EDM type of the property. This works perfectly if the type is specified after said property, but if it is before then it gets overwritten.
For instance, the code bellow sets the EDM type accordingly. Even through I pass an integer the OData type of the property is set to string and a string is returned.
One way to specify the EDM type of a property is by providing an additional
propertyName + "@odata.type"
value which tells the EDM type of the property. This works perfectly if the type is specified after said property, but if it is before then it gets overwritten.For instance, the code bellow sets the EDM type accordingly. Even through I pass an integer the OData type of the property is set to string and a string is returned.
On the other hand, if I specify the EDM type before it is ignored and an integer is stored.
I have already created a PR fixing this: #34. For more information please see azure-cli/8032 Inserting Entity Sets Unexpected OData Type for Numeric Values.
The text was updated successfully, but these errors were encountered: