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

Fix bug coercing boolean strings #126

Merged
merged 1 commit into from
Sep 4, 2024
Merged

Fix bug coercing boolean strings #126

merged 1 commit into from
Sep 4, 2024
+37 −7

Commits on Sep 4, 2024

  1. Fix bug coercing boolean strings 

    - fields with a type of T::Boolean were getting caught in the T.any conditional block and failing to activate the BooleanCoercer class. I moved the `select_coercer_by` call up to the serializer so we can handle the case where the type alias matches a coercer, falling back to checking each of the individual types in the alias if no top-level coercer is found.
    @jeremyshearer
    jeremyshearer committed Sep 4, 2024
    Configuration menu
    Copy the full SHA
    e484f5e View commit details
    Browse the repository at this point in the history