IF you can't change what the api is sending (this is not a VS forum so
can't help you there), then you can reference the value attribute on the
angular side to match what you need on the scope.
$http.get('/some/url', function(response){
$scope.steps = response.value;
})
On Wednesday, March 19, 2014 10:33:09 PM UTC-6, Brian Lewandowski wrote:
>
> Having trouble now that I've moved my project from Web API to Web API 2.
> The new oData seems to have made changes to the objects and how they
> appear in the scope.
>
> This is how it used to look using Batarang on old Web API:
>
> steps:
> [ {
> id: 1
> objectType: 3
>
>
>
> and here is how it looks with Web API 2:
>
> steps: {
> odata.metadata: http://localhost:5496/odata/$metadata#step
> value:
> [ {
> id: 1
>
> So my old bindings of {{step.id}} for example are no longer working.
> How would I structure the bindings with this new syntax? Or is there
> something I can do in Visual Studio to return the object to its original
> structure?
>
> Thanks.
>
--
You received this message because you are subscribed to the Google Groups
"AngularJS" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/angular.
For more options, visit https://groups.google.com/d/optout.
