DATAGO-66413: Rename correlationId -> commandCorrelationId #137
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
CameronRushton
temporarily deployed
to
build_pr
GitHub Actions
Inactive
CameronRushton
changed the title
|
SonarQube Quality Gate
|
moodiRealist
approved these changes
Dec 6, 2023
gregmeldrum
approved these changes
Dec 7, 2023
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.
What is the purpose of this change?
correlationId is being clobbered by the Id in MopMessage. We didn't intend for it to override this value, so we must rename it.
How was this change implemented?
Renamed correlationId -> commandCorrelationId
How was this change tested?
Manually in a dev environment, sending a request to the EMA and verifying the response back.
Is there anything the reviewers should focus on/be aware of?
None