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
My questions are, why are those strings not following the spec, and is there any way for me to follow the spec with the current code? Or is this a bug in the library? I don't understand how this is working for other people.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Using v7 of the library, in my odata controllers the PageResult() returns data according to spec. E.g. "@odata.nextLink": , "@odata.count": , etc.
When I upgraded to v8, PageResult() returns invalid odata spec data. E.g. "nextPageLink": , "count": , etc.
I downloaded the AspNetCoreOdata source and changed the three WritePropertyName() string values in the Write() method in this file to follow the spec: https://github.com/OData/AspNetCoreOData/blob/main/src/Microsoft.AspNetCore.OData/Results/PageResultValueConverter.cs
Which then returns OData conforming data.
My questions are, why are those strings not following the spec, and is there any way for me to follow the spec with the current code? Or is this a bug in the library? I don't understand how this is working for other people.
Updated code:
Beta Was this translation helpful? Give feedback.
All reactions