[fix] ID field usage in string representation of EasyPost objects #311
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
|
I know the code is very old, but is it possible to have a unit test for this change? |
jchen293
approved these changes
Apr 10, 2024
Justintime50
approved these changes
Apr 10, 2024
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
Previous method of reflection to retrieve the
idof anEasyPostResourceoften failed, resulting in fallback to empty string. As a result, the string representation of anyEasyPostResourcewas often an empty string.New method improves
toStringcalculation, including accounting for present/non-presentidfield (ephemeral objects).Testing
Pull Request Type
Please select the option(s) that are relevant to this PR.