mirror of https://github.com/logseq/logseq
fix: switching to another number closed value
The bug was creating a new block each time a switch was made because existing closed values didn't have a created-from-propertyexperiment/tanstack-table
parent
e55927086f
commit
a2a951ddcb
|
@ -13,6 +13,7 @@
|
|||
:block/page property-id
|
||||
:block/content value
|
||||
:block/closed-value-property property-id
|
||||
:logseq.property/created-from-property property-id
|
||||
:block/parent property-id}))
|
||||
|
||||
(defn build-closed-value-block
|
||||
|
|
|
@ -90,8 +90,9 @@
|
|||
(if new-closed-value?
|
||||
(number? id-or-value)
|
||||
(when-let [entity (d/entity db id-or-value)]
|
||||
(number? (some-> (:block/content entity)
|
||||
parse-double)))))
|
||||
(or (number? (:block/content entity))
|
||||
;; FIXME: UI concerns shouldn't be in this layer
|
||||
(number? (some-> (:block/content entity) parse-double))))))
|
||||
|
||||
(defn- property-value-block?
|
||||
[db s]
|
||||
|
|
Loading…
Reference in New Issue