Markdown mirror exports single-value properties with "Multiple values" disabled as list syntax (multi-value)
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 68/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- markdown
- Domain
- databases
Research direction
Start by reproducing the issue with a text property whose "Multiple values" setting is disabled, then inspect the Markdown mirror export path for property rendering. Compare the output with the expected single-value line myprop:: some value; done means single-value properties no longer use bulleted-list syntax while multi-value properties remain unaffected.
Written by the indexing model from the issue text.
Description
Search first
- I searched and no similar issues were found
What Happened?
In the Markdown mirror, a text property that has "Multiple values" disabled is incorrectly exported using multi-value list syntax instead of a single-value property line.
For example, instead of:
myprop:: some value
It exports as:
myprop::
- some value
Reproduce the Bug
- Create a text property on a node and ensure "Multiple values" is disabled for it.
- Assign a single text value to this property (e.g.,
myprop:: some value). - Check the Markdown mirror view or exported Markdown file for that node.
Observed: The property is rendered as a multi-value list:
myprop::
- some value
Expected Behavior
Properties with "Multiple values" disabled should be exported in the Markdown mirror as a standard single-value property line (e.g., myprop:: some value), not as a bulleted list.
Screenshots
No response
Files
No response
Browser, Desktop or Mobile Platform Information
- Platform: Linux Desktop
- Version: 2.0.1-alpha+nightly.20260917 (DB beta)
Additional Context
Affects the database-to-Markdown synchronization / mirror representation for properties.
Are you willing to submit a PR? If you know how to fix the bug.
- I'm willing to submit a PR (Thank you!)
- Dominant language
- No language data
- Stars
- 28
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from logseq/db-test
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 3/5 1-2 days Newbie friendliness 72/100
-
Difficulty 3/5 1-2 days Newbie friendliness 50/100
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
-
Difficulty 3/5 1-2 days Newbie friendliness 58/100
Similar issues
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
OpenLiberty/open-liberty#35839 ·
-
affects-9.0 found-by-ai may-affects-25.10 may-affects-26.3 may-affects-26.9 may-affects-7.5 may-affects-8.1 may-affects-8.5 severity/major sig/execution type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
antlr/grammars-v4#5014 · 1 comment ·