Exclude None values in custom license terms dump
#62
Conversation
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
Adds exclude_none=True to CustomLicense model_dump in Dataset. This ensures that None values are omitted from the terms dictionary when serializing custom license information.
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.
As pointed out in #46 by @bnavigator, this pull request introduces a minor enhancement to the serialization of license information within the
dataverse_dictmethod. Specifically, when dumping aCustomLicenseobject, any fields withNonevalues will now be excluded from the resulting output dictionary.Previously, when fields were set to
None, Dataverse would issue warnings indicating that the files could not be processed (refer to #46 (comment)). By omitting these fields from the payload, the issue has been resolved.