Fix issue with DataTransferHashMap handling missing data #3141
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
- Added null checks in `getData` and `removeData` methods to handle cases where the key does not exist. - Updated tests for `addData`, `getData`, and `removeData` to ensure proper functionality. - Improved the `displayData` method to provide clearer output. - Fixed minor formatting and documentation issues in the `DataTransferHashMap` class. Closes iluwatar#1269 (if the issue is related to an existing issue on GitHub)
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.
getDataandremoveDatamethods to handle cases where the key does not exist.addData,getData, andremoveDatato ensure proper functionality.displayDatamethod to provide clearer output.DataTransferHashMapclass.Closes #1269 (if the issue is related to an existing issue on GitHub)
What problem does this PR solve?
The
DataTransferHashMapclass was not handling cases where the key does not exist when callinggetDataandremoveData. This caused potentialNullPointerExceptions. The tests were also did not cover all edge cases related to missing data. Uncomment the following line if this PR closes some issues -->