Bug:

[tsbertalan]

(extending #509)

I have a block like

type: tree
fields: [down]
sort: neighbour-field:next
mermaid-direction: TB
depth: [0,0]

It almost seems to work, but there is one node C out of place in the order (and another E for which that order is not defined that seems to be arbitrarily slotted in where C should go):

In this example, A-D all have up relationships to the current page, and mutual next and prev to each other. E has up to the current page, but nothing else.

I expect A-D to be listed in order, with E shown anywhere in there, but I get instead C,A,B,E,D

A clear and concise description of what the bug is.

To Reproduce

Not sure; I tried making a minimal vault to show this, and it sorts like A,B,C,E,D, which is fine.

Expected behavior

Nodes should list order by their next/prev relationships.

Screenshots

Here, the block

type: mermaid
fields: [down,next]
merge-fields: true
mermaid-direction: TB
depth: [0,99]

correctly shows the next relationships.

Desktop (please complete the following information):

• OS: Win 11
• Breadcrumbs version:
• Obsidian version: [e.g. 1.5.12]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Breadcrumbs version: Says 3.6.11, but settings page looks like the below. I guess I downloaded this from git.
• Obsidian version: 1.7.4 (same installer version)

[michaelpporter]

@tsbertalan is this still and issue for you in the newer v4 betas?

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 10 days.