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.

Sign up for GitHub

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

Jump to bottom

Fixed #33406 -- Avoided creation of MaxLengthValidator(None) when resolving Value.output_field for strings. #15277

Merged
merged 2 commits into from
Jan 4, 2022
Merged

Fixed #33406 -- Avoided creation of MaxLengthValidator(None) when resolving Value.output_field for strings. #15277

merged 2 commits into from
Jan 4, 2022

Commits on Jan 4, 2022

  1. Refs #33406 -- Added test for not creating broken validators when res… 

    …olving Value.output_field.
    @kezabelle @felixxm
    kezabelle authored and felixxm committed Jan 4, 2022
    Configuration menu
    Copy the full SHA
    b894199 View commit details
    Browse the repository at this point in the history

  2. Fixed #33406 -- Avoided creation of MaxLengthValidator(None) when res… 

    …olving Value.output_field for strings.

This brings the behaviour in line with Field subclasses which append to
the validators within __init__(), like BinaryField, and prevents the
creation of a validator which incorrectly throws a TypeError, if it
were used.
    @kezabelle @felixxm
    kezabelle authored and felixxm committed Jan 4, 2022
    Configuration menu
    Copy the full SHA
    0ed2919 View commit details
    Browse the repository at this point in the history