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
feat: support incremental configuration synchronization client #5288
base: master
Are you sure you want to change the base?
feat: support incremental configuration synchronization client #5288
Changes from 12 commits
4e8a699
26a0e1b
2dd9352
b13968c
24bda1d
cf5145f
8cafda2
72676c0
065a092
e69f098
a6a412a
07bb41c
a4b356c
5e37f55
8512776
5a76da9
a4a2d05
04f50ac
1b20e4e
4f06613
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.
🛠️ Refactor suggestion
Ensure robust handling of
clientSideReleaseKey
Consider adding validation to handle cases where
clientSideReleaseKey
might benull
or empty to prevent potentialNullPointerException
or unexpected behavior when the client does not provide areleaseKey
.Suggested change:
Add a null or empty check before processing
clientSideReleaseKey
: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.
Handle empty or null
historyReleases
gracefullyCurrently, the code checks if
historyReleases != null
, but does not handle the case wherehistoryReleases
is empty. This could lead to scenarios where incremental synchronization is attempted without any historical releases, potentially causing incorrect behavior.Suggested solution:
Modify the condition to check for empty
historyReleases
and handle accordingly: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.
Implement or document the null return behavior.
The current implementation returns
null
without explanation, which could lead to NullPointerException in calling code. Consider:Example improvement: