Skip to content

[BUGFIX] Do not deserialize when a relationship named type exists - #3814

Merged
bmac merged 1 commit into
warp-drive-data:masterfrom
andycrum:fix-type-relationship
Oct 3, 2015
Merged

[BUGFIX] Do not deserialize when a relationship named type exists#3814
bmac merged 1 commit into
warp-drive-data:masterfrom
andycrum:fix-type-relationship

Conversation

@andycrum

@andycrum andycrum commented Oct 2, 2015

Copy link
Copy Markdown
Contributor

69dca0c fixed this for attributes named type, but the RESTSerializer
was still trying to deserialize relationships with that name as
polymorphic, which was causing errors for anyone having a domain
model called "Type".

cc @bttf @bmac

69dca0c fixed this for attributes named 'type', but the RESTSerializer
was still trying to deserialize relationships with that name as
polymorphic, which was causing errors for anyone having a domain
model called "Type".
@andycrum

andycrum commented Oct 2, 2015

Copy link
Copy Markdown
Contributor Author

I believe this fixes #3784

@bmac

bmac commented Oct 3, 2015

Copy link
Copy Markdown
Contributor

Looks great. Thanks @andycrum.

bmac added a commit that referenced this pull request Oct 3, 2015
[BUGFIX] Do not deserialize when a relationship named `type` exists
@bmac
bmac merged commit e8b426e into warp-drive-data:master Oct 3, 2015
@jevanlingen

Copy link
Copy Markdown

👍

@jevanlingen

Copy link
Copy Markdown

Btw, can this fix be applied to the 1.13.x branche too?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants