Display full title hierarchy in backlinks

[pierrefevrier]

It would be great to let user choose to display full title hierarchy in backlinks.

Consider the following example :

# Subject 1

## 2022-11-03
- Some text
- [ ] one task of subject 1

## 2022-11-08
- Some other text
- [ ] another task of subject 1

# Subject 2

## 2022-11-03
- Some text
- [ ] one task of subject 2

## 2022-11-08
- Some other text
- [ ] another task of subject 2

Current rendering :

It would be more useful for me to see something like (I really need this) :

Related comment : #1166 (reply in thread)

[claremacrae]

Thanks for logging the separate request!

What's the significance in the screenshots between backlinks starting with 'Untitled 3' in the first one vs starting with 'heading 1 name' in the second one?

It looks to me like in the second one, you are specifically asking for the file name not to be displayed? Is that really the intention?

I believe that the current behaviour for backlinks is to display:
filename > previous heading

I initially thought you were proposing to add an option to make it possible to have:

filename > heading level 1 > heading level 2 etc

But now I am not so sure.

A picture is worth a 1000 words, but the words are useful too 🤣

Please could spell out in more detail what the request is? Many thanks in advance!

Also, are you imagining this is a global setting, for all tasks results blocks?

[pierrefevrier]

You are right, the first propose that give value is to have :
filename > heading level 1 > heading level 2 etc

In some situations, I even don't need to display filename since I scope the tasks to the current file, resulting in the second screenshot.

[samqbush]

@pierrefevrier / @claremacrae Sorry to necro this thread, but was there ever a solution to getting the full hierarchy in the backlink?
filename > heading level 1 > heading level 2 etc

Is it possible with CSS?

[claremacrae]

@pierrefevrier / @claremacrae Sorry to necro this thread, but was there ever a solution to getting the full hierarchy in the backlink? filename > heading level 1 > heading level 2 etc

Is it possible with CSS?

No.

[mkpaz]

I need the opposite. Since, I don't use daily notes, I'd like to hide all headings from the backlink and only see the file (project) name. So, if this implemented there should be a way to hide the part of the hierarchy without hiding the backlink. It could be done by passing optional param to the hide backlink command.

• hide backlink - hides backlink completely, equivalent to hide backlink 0
• hide backlink 1 - keep backlink, but hide all headings up to h1
• and so forth

Another option is to render backlink HTML like this <a href="link"><span class="filename">Filename</span><span class="heading-1">&gt; Heading 1</span> ... etc</a>, so one could use CSS to hide he/she doesn't want to see. But the latter will hurt inexpirienced users.

[claremacrae]

Thank you for the suggestions.

[mdbraber]

@claremacrae I'd like this approach as a workaround which would also be able to address some issues like:

#473
#451 (reply in thread)

Although I could see that BacklinkField.ts would need some refactoring if that would be implemented, maybe an option to enabled/disable showing headings would be easier to implement?

[claremacrae]

Thank you for the suggestions.

Actually @mdbraber, on reflection, since this is specifically a request for "Display full title in background", any requests for different things are effectively invisible.

The volume of requests for Tasks is hard enough to manage already, without having to remember which requests contain more than one different topic...

[claremacrae]

I probably should have mentioned @mkpaz in the above...

[claremacrae]

The following would need to be implemented before this could be done, since currently each task only knows about the immediately-preceding heading:

• Filter tasks by all applicable headings #209

[claremacrae]

Anyone interested in this topic can find related suggestions by searching for the the label scope: backlinks in:

• Issues
• Discussions > Ideas: any feature requests....

Also related is the label scope: parsing markdown, for reading any changes to how Tasks interprets content from Obsidian notes.

Please try to keep each of these to a single topic, or at least not broaden any of them... Thanks in advance.