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
Because MongoDB's BSON serializer is global, there's a chance (risk!) that any conventions applied at a global level will apply to how sagas are serialized. Also, this might actually be what the user wants 🙂
BUT it poses a problem e.g. when using camel-cased field names in BSON, because Rebus will e.g. be querying for a field named CorrelationId, which is the name in the C# class, but in BSON it's represented as correlationId.
By doing an initial dummy-serialization of an empty instance of the saga data type, it might be possible to deduce the actual resulting field names corresponding to the saga's fields (at least if it's only the casing that's changed).
The text was updated successfully, but these errors were encountered:
Because MongoDB's BSON serializer is global, there's a chance (risk!) that any conventions applied at a global level will apply to how sagas are serialized. Also, this might actually be what the user wants 🙂
BUT it poses a problem e.g. when using camel-cased field names in BSON, because Rebus will e.g. be querying for a field named
CorrelationId
, which is the name in the C# class, but in BSON it's represented ascorrelationId
.By doing an initial dummy-serialization of an empty instance of the saga data type, it might be possible to deduce the actual resulting field names corresponding to the saga's fields (at least if it's only the casing that's changed).
The text was updated successfully, but these errors were encountered: