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

[BUG]: BC-tag-note is case sensitive + points in the wrong direction #219

Closed
chrisgrieser opened this issue Dec 19, 2021 · 5 comments
Closed

Comments

@chrisgrieser
Copy link
Contributor

Both issues are recorded here, BC-tag-note seemingly makes all notes with the tag point down to the note, instead of up, and it seems to be case sensitive, while Obsidian doe snot care about case when it comes to tags.

Screen.Recording.2021-12-19.at.15.33.25.mov
@SkepticMystic
Copy link
Owner

Regarding the direction issue, this has been addressed in a previous post. You need to use the BC-tag-note-field: key to indicate the direction. I agree that the default is not intuitive, but there is the option to specify a field.

About case-sensitivity, yeah that's a bug! Thanks :)

@chrisgrieser
Copy link
Contributor Author

then the wiki might be a bit outdated. It says there that adding BC-tag-note-up:, but after your comment here I tried out a bunch of options till I figured out that its BC-tag-note: down I need to add 😅

@chrisgrieser
Copy link
Contributor Author

okay, now I am a bit confused. it seems that whatever I do, BC-tag-note always points up instead of down? Am I missing something or what exactly is the proper syntax? 🤔

Screen.Recording.2021-12-19.at.20.48.10.mov

@SkepticMystic
Copy link
Owner

@chrisgrieser the syntax to override the default tag-note direction is BC-tag-note-field: field

@chrisgrieser
Copy link
Contributor Author

thank you, that finally did it! Now I can finally properly set up my hierarchies! 😭

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

2 participants