Problem using Guid datatype in OData v4 query about odataangularresources HOT 9 CLOSED

I fixed it for me by changing this code bit:

if(this.type.toLowerCase() === "guid"){
    return "guid'"+this.value+"'";

to

if(this.type.toLowerCase() === "guid"){
    return this.value;

Although that will probably break functionality with previous OData versions, and shouldn't be considered a generic fix.

from odataangularresources.

Are you sure it's 4.0? Did you check the response header of odata ( which includes the version)

from odataangularresources.

Thanks for the tip. I'm using ODatav4 and I'm requried to use the guid'...' syntax.
So I won't change the library to use that format.

from odataangularresources.

He is right though: http://docs.oasis-open.org/odata/odata/v4.0/errata02/os/complete/part2-url-conventions/odata-v4.0-errata02-os-part2-url-conventions-complete.html#_Toc406398153

I'm also facing the same issue when using it in a $filter. According to the specs, guid seems to be used as a integer which is correct ( logic wise). The library doesn't work when using an odata v4 $filter.

Double checked it right now.

from odataangularresources.

Theirs a partial fix in my fork NicoJuicy@9f1f195

Updated the specs and code.
Now tested it out in practise and pushed it.

from odataangularresources.

So what you're telling me is that because whatever server-side OData implementation you're testing against does OData v4 wrong, you won't do it right?

from odataangularresources.

I acknowledged my mistake and accepted a pull requests that fixes it already : #17
You can bower update to get the latest version with the fix.

from odataangularresources.

Pardon me, all I saw was your comment where it said that you won't change the library to use that format. Thanks, sorry for being misinformed.

from odataangularresources.

@devnixs thanks for immediatly putting it into bower :)

from odataangularresources.