John
Results
3
comments of
John
Our use case would benefit from this as well - we use jetstream as a first-tier persistence layer for client-created data, and our clients use the timestamp both as stored...
Agreed, we can handle such a case
Is this still not supported? I can see how reimplementing `parseEngineMessage` works, but what about publishing with a custom parser?