Text property with no default set for the available choices stops selection in the DB table

[C0ntr0lledCha0s]

Search first

• I searched and no similar issues were found

What Happened?

When I'm trying to assign a value from a property's 'Available choices' in the database table, I'm unable to trigger the selection dropdown (not showing an empty value placeholder in the DB row).

This behaviour is resolved if a 'default choice' is selected but comes back if the default choice is deselected.

Reproduce the Bug

msedge_oFGRskcZtH.mp4

Expected Behavior

Can select a choice in the DB table row when the default choice is empty.

Files

No response

Browser, Desktop or Mobile Platform Information

logseq/logseq@7b8a9d4

Additional Context

No response

Are you willing to submit a PR? If you know how to fix the bug.

• I'm willing to submit a PR (Thank you!)

[tiensonqin]

@C0ntr0lledCha0s Thank you for the report, can you give it another try? Please create a new graph to verify if it works.

[C0ntr0lledCha0s]

@tiensonqin On version logseq/logseq@a551370, I can now edit the field in the datatable.
However this may have led to unexpected behaviour as I would expect "Nodes with property" to show empty values if a default value is not set but they do not (they are shown as a 'Linked reference' only. On entering a value they populate in the table on a browser refresh)

msedge_5RVn1cZfUE.mp4

[logseq-cldwalker]

However this may have led to unexpected behaviour as I would expect "Nodes with property" to show empty values if a default value is not set but they do not

Hi. I agree there is an inconsistency here. When a node has an empty property value e.g. when created from a property table, it shows up in the property table. When a node has an empty property value through a tag, it doesn't show up in the property table. We should either treat an empty property value as a property having a value or not . We'll look into this

[logseq-cldwalker]

@C0ntr0lledCha0s The 2nd issue you noticed with property table results has been fixed. Should be up on test in ~10m. Closing but happy to reopen if there's still an issue