-
Notifications
You must be signed in to change notification settings - Fork 21
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
Doesn't seem to work with Metadata? #13
Comments
It works fine on correctly-formatted YAML in the field that Obsidian parses. To check the format, create a new note with just the metadata from a note you had trouble with, then check that if you search for If it doesn't show up, then your tags are not being recognized by Obsidian, and therefore not recognized by Tag Wrangler, either. Some possible things that could cause that:
If your test note does show up in a
If your test doesn't show up in the search or "Tags" metadata, you will need to correct your YAML formatting in any affected notes for Tag Wrangler to work. If it's not clear what's wrong with the formatting, you can again paste a block like the above here and I'll see if I can help you. |
This is my Metadata: |
Please follow the instructions I gave, both to check the formatting and to copy the entirety of the exact metadata in a fenced code block in your reply, along with the results of the tests I described. Thanks. |
Apologies, I am a non-coder. I did all the tests and there is nothing wrong with the formatting. All the tags show up in the tag pane and when I change the tag (for instance here if I change C/2 to test) it updates in the pane also. So as far as I can see the metadata is working alright, or am I missing something?
Thank you again for taking the time to help me I appreciate it :) |
Thank you. I've released 0.4.4 to fix the main problem, which was that some of the values in your Unfortunately, you will likely not find my fix to be entirely satisfactory, since it will not maintain the linkages you've set up when you rename a tag: it will simply replace the ---
Quality: &a C/2
RLEVEL: &b
Utility: &c
Field: &d
Type: &e ⚪/Figure
tags: [ test, *b, *c, *d, *e ]
--- Which I am guessing is not what you want. The method I am using to update the tags field is not smart enough to be able to tell that you want the other values to be changed as well, and I don't see any easy way to change that in the near future. |
Thanks! I don't have a problem with this implementation! Do you have any suggestion how I could alter my workflow where I could keep variable fields with tags, should I separate tags from the metadata? I'm just thinking if there's a way to do this without storing variables and using them as tags in an array |
I'm not sure I understand your question, but I think the answer is, "it depends on what you're trying to accomplish". For example, I have no idea why you're doing it the way you are now, so I'm not sure I know how to suggest doing it better. 😉 |
Tags that are edited don't seem to edit the tags in the meta-data. I am extremely dependent on your brilliant plugin for all my workflow management and updating and so I am quite cautious now to put tags in the metadata rather than the body. I'm not sure if there is a trivial fix to this?
The text was updated successfully, but these errors were encountered: