Skip to content

Fix ModelSerializer custom named fields with source on model #5388

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Sep 4, 2017

Conversation

jonsongoffwhite
Copy link
Contributor

@jonsongoffwhite jonsongoffwhite commented Sep 4, 2017

Description

Fixes #5389

Includes a test that fails on master, passes before #5138, and now passes with included fix.

@jonsongoffwhite jonsongoffwhite changed the title Fix/named source Fix ModelSerializer custom named fields with source on model Sep 4, 2017
@carltongibson
Copy link
Collaborator

Hi @JHG14 Could I trouble you for a description please? Thanks!

Copy link
Collaborator

@carltongibson carltongibson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep. Looks good. Thank you.

Copy link
Collaborator

@carltongibson carltongibson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jonsongoffwhite
Copy link
Contributor Author

@carltongibson Should be good now!

@carltongibson carltongibson added this to the 3.6.5 Release milestone Sep 4, 2017
@carltongibson carltongibson merged commit 71ad99e into encode:master Sep 4, 2017
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.

ModelSerializer custom named field source evaluates to True instead of field_name
2 participants
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy