Skip to content

Conversation

bor3ham
Copy link
Contributor

@bor3ham bor3ham commented Jan 25, 2017

To consider child_relation, eg. the default reverse relationship created by m2m. Otherwise it appears to fall back to the parent serializer type.

To consider child_relation, eg. the default reverse relationship created by m2m. Otherwise it appears to fall back to the parent serializer type.
@codecov-io
Copy link

codecov-io commented Jan 25, 2017

Current coverage is 91.55% (diff: 100%)

Merging #317 into develop will increase coverage by <.01%

@@            develop       #317   diff @@
==========================================
  Files            49         49          
  Lines          2330       2332     +2   
  Methods           0          0          
  Messages          0          0          
  Branches          0          0          
==========================================
+ Hits           2133       2135     +2   
  Misses          197        197          
  Partials          0          0          

Powered by Codecov. Last update c869f34...c50eb8f

@bor3ham
Copy link
Contributor Author

bor3ham commented Feb 20, 2017

Don't think this is actually required, issue seems to be fixed by using provided json_api model serializers.

@bor3ham bor3ham closed this Feb 20, 2017
@bor3ham bor3ham deleted the patch-1 branch March 16, 2017 02:36
@Darkheir
Copy link
Contributor

I still have the problem on reverse Many to Many relations using a Through table and I think this commit may fix the issue ...

@Darkheir
Copy link
Contributor

Actually it doesn't fix the issue if in the serializer the field is set as read only.

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