logseq / logseq/db-test

Using `Name` to sort in table views breaks/disables sorting by anything else.

Open
#1,100 2 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?

Using `Name` to sort in table views breaks/disables sorting by anything else. Before using the `Name` field to sort, everything works. The moment you sort by `Name` nothing else (like `Created At`, `Updated At` etc.) works again in that view. You have to delete it and create a new View. But that View will also break if you sort by `Name`.

### Reproduce the Bug

1. Go to a table view like in `#Property` or `#Tag`.
2. Try sorting by `Created At` or `Updated At`. Everything works.
3. Now sort by `Name`. Sorting by name works but now everything else stops working in that View.

### Expected Behavior

Sorting should work as expected.

### Screenshots

_No response_

### Desktop or Mobile Platform Information

AppImage 2.0.1 Beta

### 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 a table view like #Property or #Tag, sorting by Created At or Updated At before and after sorting by Name. Trace the table-view sorting behavior and verify that sorting by Name no longer prevents the other fields from sorting in the same view.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.