Dev/core#2524 Fix seriazliation parameter exception in APIv3 #22934
Conversation
This file contains 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
|
(Standard links)
|
colemanw
reviewed
Mar 13, 2022
|
This looks good @adriano66 - are you able to squash these 4 commits before we merge? |
This fixes the "'0' is not a valid option for field serialize" exception in APIv3 as 0 is a valid, default value set in the DB This allows passing whole custom field data as a parameter to the custom field update method without getting an exception Co-authored-by: colemanw <coleman@civicrm.org>
4dc7a35 to
b6e5092
Compare
|
@colemanw Sure, done. |
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.
Overview
This fixes the "'0' is not a valid option for field serialize" exception in APIv3.
0 is a valid, default value set in the DB.
This allows passing whole custom field data as a parameter
to the custom field update method without getting an exception.
https://lab.civicrm.org/dev/core/-/issues/2524