feat(core-data): Event ID has to be pre-populated #2695
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.
Signed-off-by: Cloud Tsai [email protected]
PR Checklist
Please check if your PR fulfills the following requirements:
make test
has completed successfullyPR Type
What kind of change does this PR introduce?
What is the current behavior?
Event ID will be generated before storing into the database
Issue Number: Fix #2684
What is the new behavior?
In V2 API, Event ID has to be UUID and pre-populated.
Adopt the latest go-mod-contracts to include this validation.
Modify the related unit test to verify this feature.
Remove the UUID assignment before storing into the database.
Remove checksum and correlation id from Event model.
Does this PR introduce a breaking change?