logseq / logseq/db-test

The # row-number column is not preserved when returning to a page

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

Nobody has claimed this yet.

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

Description

Search first
  • I searched and no similar issues were found
What Happened?

In Table View, there is a column option called # that automatically assigns a number to each row. After enabling this # column, the setting is lost when switching to another view or navigating to another page.

When I return to the original page, the # column is no longer selected, so the row numbers are no longer displayed.

Reproduce the Bug
  1. Open a page with a Table View.
  2. Enable the # column to display row numbers.
  3. Switch to another view or navigate to another page.
  4. Return to the original page
Expected Behavior

The # column should remain enabled and continue displaying row numbers.

Screenshots

No response

Files

No response

Browser, Desktop or Mobile Platform Information

Logseq 2.0.1

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 issue in Table View and trace how the # column selection is stored when switching views or navigating between pages. Done means the # column remains selected and row numbers are still displayed after returning to the original page.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.