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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
solve the problem of duplicate comments and blank lines #5232
solve the problem of duplicate comments and blank lines #5232
Changes from 3 commits
1c7dcf8
444ce9b
859bbdb
904ab87
09b4601
fdc5e60
48da7db
1c024df
84180a2
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Prevent potential
NullPointerException
when comparing string valuesIn the
handleNormalLine
method, the condition on line 180~ comparesnewValue
andoldItem.getValue()
:If
oldItem.getValue()
isnull
, this could result in aNullPointerException
. To safely handle possiblenull
values, useStringUtils.equals(newValue, oldItem.getValue())
, which handlesnull
comparisons gracefully.Apply this diff to prevent the potential exception:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🛠️ Refactor suggestion
Consider filtering out blank keys during map creation
Instead of removing entries with blank keys after creating
oldKeyMapItem
, consider filtering out items with blank keys when constructing the map. This can improve code clarity and prevent unnecessary entries from being processed.You can modify the map creation as follows:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Use
Objects.equals
to prevent potentialNullPointerException
If
oldItem.getValue()
orvalue
could be null, using!oldItem.getValue().equals(value)
may cause aNullPointerException
. Consider using!Objects.equals(oldItem.getValue(), value)
to safely compare values.Ensure you have imported
java.util.Objects
.