Skip to content

Make the aliases handling to be equivalent of obsidian #333

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

Open
danielo515 opened this issue Jan 18, 2024 · 2 comments
Open

Make the aliases handling to be equivalent of obsidian #333

danielo515 opened this issue Jan 18, 2024 · 2 comments

Comments

@danielo515
Copy link

🚀 The feature, motivation and pitch

Hello, and thank you for this plugin.
Being able to take obsidian notes from VIM is such a quality of life improvement. I can't stand how buggy their vim bindings are.
I noticed a lot of errors when trying to link notes, making my experience awful. Because I use notify 5k warnings takes a long to render and clear.
The reason of the warnings was what your plugin considers malformed aliases. However, all my aliases work neat within obsidian. I made some tests with their api and they are able to handle all this cases just fine:

aliases: single alias
aliases: comma, sep, list
aliases: [comma, sep, list, with delimiters]
aliases:
 - yaml
 - list

I think it will be nice if this plugin could also understand all that.

Alternatives

I had to lower the debug level because neovim was becoming unusable due to the warnings. That is my alternative for now 😄

Additional context

No response

epwalsh added a commit that referenced this issue Jan 18, 2024
@epwalsh
Copy link
Owner

epwalsh commented Jan 18, 2024

Hey @danielo515, your 3rd and 4th example are definitely supported. If you get an error with those cases then that means there's a bug in our YAML parser. bf8083f adds support for the 1st example as well, but the 2nd example is not a valid YAML list, so I don't think we'll add support for that.

@danielo515
Copy link
Author

I think most of my errors are coming from the first error, so that are good news

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

No branches or pull requests

2 participants