[Platform] Improvements on Uuid handling & MessageNormalizer
#1001
+52
−41
Conversation
This file contains hidden or 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
Guikingone
changed the title
MessageNormalizer
Guikingone
requested review from
Nyholm,
OskarStark and
chr-hertel
as code owners
carsonbot
added
Bug
OskarStark
changed the title
MessageNormalizerMessageNormalizer
OskarStark
reviewed
Nov 27, 2025
Guikingone
force-pushed
the
refactor/message_identifier
branch
4 times, most recently
from
f4e9f4b to
5896900
Compare
Guikingone
force-pushed
the
refactor/message_identifier
branch
from
5896900 to
d0bc545
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Summary:
MessageNormalizer::denormalize(), it looks like we're recreating a newUuid::v7()in the constructorIdentifierAwareTraitthat expose two methodsgetId()andwithId, the last one allows to either specify an exiting Uuid or use av7one