Noticed that when consuming events from a stream built by a projection, with the "resolveLinkTos" option set to true, the deserializer appears to ignore what's in the link: { } structure entirely. This means that I can't get at the event numbers from the projection stream, just the ones from the stream that the link-resolved event comes from. So there's no way to track sequential event numbers in a projection stream if I also want the linked events resolved.
x-cubed
commented
8 years ago
Noticed that when consuming events from a stream built by a projection, with the "resolveLinkTos" option set to true, the deserializer appears to ignore what's in the link: { } structure entirely. This means that I can't get at the event numbers from the projection stream, just the ones from the stream that the link-resolved event comes from. So there's no way to track sequential event numbers in a projection stream if I also want the linked events resolved.
Relevant code: lib/connection.js - unpackResolvedEvent(resolvedEvent) -> return unpackEventRecord(resolvedEvent.event);
See Google Groups issue I raised: https://groups.google.com/forum/#!topic/event-store/MIsb87kjvzE