Closed raquo closed 1 year ago
The problem is specific to FetchStream. As a temporary workaround you can replace FetchStream.get(...)
with EventStream.unit().flatMap(_ => FetchStream.get(...))
. This initializes FetchStream in a new transaction created by flatMap, avoiding the bug.
render
)renderOnDomContentLoaded
)I'm not yet sure what the exact problem is, or whether it's specific to FetchStream or not.