Remove DateDeserializer #334
Merged
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
Justintime50
requested changes
Sep 12, 2024
jchen293
changed the title
Justintime50
approved these changes
Sep 16, 2024
nwithan8
approved these changes
Sep 16, 2024
nwithan8
changed the title
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.
Description
This PR closes #333. The DateDeserilizer was created to handle an edge case from our API response for date format. We have corrected the date format at the API level, so the DateDeserilizer has been removed.
Testing
Re-recorded cassettes to ensure we have the latest response for Claims, date was parsed correctly
Pull Request Type
Please select the option(s) that are relevant to this PR.