Skip to content
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

Resolve empty HTML charfield behavior. #3321

Merged
merged 1 commit into from
Aug 24, 2015
Merged

Conversation

tomchristie
Copy link
Member

Closes #3318.

@tomchristie tomchristie added this to the 3.2.3 Release milestone Aug 24, 2015
@@ -385,8 +385,10 @@ def get_value(self, dictionary):
# If the field is blank, and null is a valid value then
# determine if we should use null instead.
return '' if getattr(self, 'allow_blank', False) else None
elif ret == '' and self.default:
return empty
elif ret == '' and not self.required:
Copy link
Collaborator

Choose a reason for hiding this comment

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

Maybe we could add a link to the two bugs that lead to this test ?

Copy link
Member Author

Choose a reason for hiding this comment

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

I'll link to the tests around CharField behaviors, yup. Lemme wait til we have a tagged version to point at.

tomchristie added a commit that referenced this pull request Aug 24, 2015
Resolve empty HTML charfield behavior.
@tomchristie tomchristie merged commit b271946 into master Aug 24, 2015
@tomchristie tomchristie deleted the empty-charfield-html branch August 24, 2015 09:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants