logseq / logseq/db-test

'enable property history' has no effect

Open
#1,120 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
28
Forks
2
PR merge metrics
No merged PRs in 30d

Description

### Search first

- [x] I searched and no similar issues were found

### What Happened?

Adding the enable property history property to a property page and setting it to enable does not seem to have any effect (except for the status property)

Is there any documentation explaining what the enable property history property is supposed to do and how it works?

### Reproduce the Bug

1. Create a property page.
2. Add the enable property history property to the property page.
3. Set its value to enable.
4. Use the property on a node and change its value.
5. Check the node for a timestamp indicating when the property value was changed.

### Expected Behavior

The time when the property value changes should be displayed next to the node, similar to how it is displayed for the status property.

### Screenshots

_No response_

### Files

_No response_

### Browser, Desktop or Mobile Platform Information

_No response_

### 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!)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the listed property-page and node steps, then inspect how the enable property history property is handled when a node value changes. Compare the result with the status property behavior and check any existing documentation for the property. Done means property changes display their timestamps next to the node, or the intended behavior is documented clearly.

Written by the indexing model from the issue text.

Assessment

Domain
database
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.