Check for non-empty params and return changeset in cast_attachments#55
Merged
achempion merged 3 commits intoelixir-waffle:masterfrom Mar 21, 2025
Merged
Conversation
Contributor
Author
|
Updated the code, I incorrectly assumed there should always be something in the params to cast, while attachments may as well be optional. Just returning the changeset as-is if there is nothing to cast now. |
|
Works & solves the warning for us! |
Member
|
Thanks for the fix! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #54
Previously, the documentation stated a default of
:invalidfor the changeset function (and in extension the cast_attachments function).The
cast_attachmentsfunction would then check the params for:invalidand return:invalid, which would get passed to theEcto.Changeset.castfunction as the params argument.Since the improved type checking of Elixir 1.18 this causes a typespec warning, since the
Changeset.castfunction's signature does not specify:invalidas a valid type for the params.Solved by checking if the params are a non-empty map and returning a proper Changeset error: