fix: update serialization for DestinationDefinitionRead object #3
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.
Update Serialization for DestinationDefinitionRead Object
Summary
This PR addresses serialization issues in the
DestinationDefinitionRead
object. The serialized JSON response was missing thecustom
field and therelease_date
was being deserialized incorrectly as aString
instead ofVec<u16>
.Changes
custom
field to serialized outputrelease_date
to useVec<u16>
instead ofString
Example Serialized Response
Next Steps
After merging this PR, a new version of the library should be built and published to crates.io.
Please review and if all looks good, proceed with merging.