We're resetting expansion state when :nextjourna/hash is changing on a result. The hash is computed starting from the presented value using nippy/freeze. It turns out that adding pagination continuation functions (#421) as metadata on the presented result broke nippy serialization and we'd get a fresh hash (a gensym) on each call to show. We can fix it by excluding metadata when freezing.
Fix #547.
We're resetting expansion state when
:nextjourna/hashis changing on a result. The hash is computed starting from the presented value using nippy/freeze. It turns out that adding pagination continuation functions (#421) as metadata on the presented result broke nippy serialization and we'd get a fresh hash (a gensym) on each call to show. We can fix it by excluding metadata when freezing.