Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add setting for linking headings #30

Closed
kometenstaub opened this issue Aug 5, 2023 · 8 comments
Closed

Add setting for linking headings #30

kometenstaub opened this issue Aug 5, 2023 · 8 comments

Comments

@kometenstaub
Copy link
Owner

private surroundWithQuotes(headingsArray: string[]): string[] {

@brimwats
Copy link

if I understand this right, I came here to +1 this; I think it means allowing the LCSH to be linked like [[English language--Pronoun]], yeah?

@mariomui
Copy link

heading: China--History--An Lushan Rebellion, 755-763

It is hard for other plugins to identify whether or not this heading is a single heading or an array.
Well, i know it's a single heading but without the quotes it would be difficult. In fact, it might be easier to default it to an arraw.
heading

  • ....

That implicitly allows outside application to infer that the item is a single item.

@mariomui
Copy link

i would also like to code something that would manually parse the heading into broader--related--narrow because not having the same api across the notes makes it difficult for outside apps to hook into the notes.

For instance, Breadcrumbs can establish hierarchies creating an auto discovery tree.

Screen Shot 2023-09-09 at 7 17 45 PM

The note on the left a "browsable" api whereas the note on the right only has "heading". Since the heading encodes the data necessary for creating a hierarchal discovery tree, I cannot automate a majority of my pkm, notes with only the "heading" metadata cannot link to related or narrower disciplines.

@kometenstaub
Copy link
Owner Author

if I understand this right, I came here to +1 this; I think it means allowing the LCSH to be linked like [[English language--Pronoun]], yeah?

Yes.

@kometenstaub
Copy link
Owner Author

kometenstaub commented Sep 10, 2023

heading: China--History--An Lushan Rebellion, 755-763

It is hard for other plugins to identify whether or not this heading is a single heading or an array. Well, i know it's a single heading but without the quotes it would be difficult. In fact, it might be easier to default it to an arraw. heading

  • ....

That implicitly allows outside application to infer that the item is a single item.

I don’t decide how it is formatted. That’s valid yaml for strings and how Obsidian formats it when using their API. I don’t see a reason to use an array when it can only be one item. That would also be a breaking change.

Edit: I don’t know why it would be hard for other plugins. There should be no issue unless they interpret strings as arrays when certain characters like commas are present. Iirc breadcrumbs does that? Obsidian used to do it, but veered away from it.

@kometenstaub
Copy link
Owner Author

i would also like to code something that would manually parse the heading into broader--related--narrow because not having the same api across the notes makes it difficult for outside apps to hook into the notes.

For instance, Breadcrumbs can establish hierarchies creating an auto discovery tree.

Screen Shot 2023-09-09 at 7 17 45 PM The note on the left a "browsable" api whereas the note on the right only has "heading". Since the heading encodes the data necessary for creating a hierarchal discovery tree, I cannot automate a majority of my pkm, notes with only the "heading" metadata cannot link to related or narrower disciplines.

I don’t understand. Is this related to this issue? Otherwise, please open a new one.

@kometenstaub
Copy link
Owner Author

Also to clarify, headings includes the relations in this case. The purpose of this is that it’s possible to navigate the relations without the need of breadcrumbs.

@kometenstaub
Copy link
Owner Author

Please tell me if this works as you expect. The feature needs to be enabled and works for broader, narrower and related headings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants