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

Contact entry not recognised if @ is in the telegram field #6

Open
mofosyne opened this issue May 3, 2023 · 2 comments
Open

Contact entry not recognised if @ is in the telegram field #6

mofosyne opened this issue May 3, 2023 · 2 comments
Labels
bug Something isn't working

Comments

@mofosyne
Copy link

mofosyne commented May 3, 2023

Just discovered that if I added @ to telegram: thinkerer like telegram: @thinkerer the contact plugin will not add the contact in... looks like a bug

Below is the minimum test file I used to replicate the issue

---
name:
  first: Test
  last: Tester
phone:
telegram: @Test
linkedin:
birthday:
last_chat:
friends:
type: contact
---
@vbeskrovnov
Copy link
Owner

Unfortunately, this is Obsidian API limitation, as a workaround you can use quotes:

---
name:
  first: Test
  last: Tester
phone:
telegram: "@Test"
linkedin:
birthday:
last_chat:
friends:
type: contact
---

But I will see if it makes sense to use custom yaml parser instead of Obsidian API.

@mofosyne
Copy link
Author

https://yaml.org/spec/1.2-old/spec.html#id2772075

commercial-at: @text
grave-accent: `text

Above would give ERROR: Reserved indicators can't start a plain scalar. as the “@” (#x40, at) and “`” (#x60, grave accent) are reserved for future use.


So yeah it will need to be a non standard YAML parser. (Or at least provide a visible indicator that this is invalid)

@vbeskrovnov vbeskrovnov added the bug Something isn't working label Aug 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants