Fix originator in indexer storer #1009
Merged
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.
Fix originator parameter passing in indexer storer
buildOriginatorEnvelopefunctions for GroupMessageStorer and IdentityUpdateStorerThe
buildOriginatorEnvelopefunctions in both group_message_storer.go and identity_update_storer.go now accept an explicitoriginatorIdparameter instead of hardcoding the originator ID values internally. The corresponding test files group_message_storer_test.go and identity_update_storer_test.go add assertions to verify that the originator node ID in envelopes matches the expected constantsGROUP_MESSAGE_ORIGINATOR_IDandIDENTITY_UPDATE_ORIGINATOR_IDrespectively.📍Where to Start
Start with the
StoreLogmethod in group_message_storer.go to see how the modifiedbuildOriginatorEnvelopefunction is called with the explicit originator ID parameter.Macroscope summarized 028fa37.