You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
feat(NewtonsoftJson): Upconvert from Case that should be a string #97
Exactly - DUs in particular are notorious; the standard encoding is sensitive to reordering of fields etc, and more, as mentioned in the linked json.net issue.
The most common thing IME is that people use random SCDUs and typesafe enums declared in common files in serialised structs. And then, once it's in the database, you're tied to that representation forever unless you're prepared to roundtrip e.g. all the events in your event store to 'fix' them, and life is short!
changed the title [-]Feature: NewtonsoftJson: Upconvert from Case that should be a string[/-][+]feat(NewtonsoftJson): Upconvert from Case that should be a string[/+]on Aug 8, 2023
Activity
deviousasti commentedon Jul 24, 2023
What's the use-case? Someone might have persisted this to their DB without checking what it actually serializes as?
bartelink commentedon Jul 24, 2023
Exactly - DUs in particular are notorious; the standard encoding is sensitive to reordering of fields etc, and more, as mentioned in the linked json.net issue.
The most common thing IME is that people use random SCDUs and typesafe enums declared in common files in serialised structs. And then, once it's in the database, you're tied to that representation forever unless you're prepared to roundtrip e.g. all the events in your event store to 'fix' them, and life is short!
[-]Feature: NewtonsoftJson: Upconvert from Case that should be a string[/-][+]feat(NewtonsoftJson): Upconvert from Case that should be a string[/+]bartelink commentedon Apr 25, 2024
Poor man's impl: