generated from obsidianmd/obsidian-sample-plugin
-
-
Notifications
You must be signed in to change notification settings - Fork 285
docs: Write up observations on Obsidian 1.9.x property reading #3491
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
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…Obsidian 1.9.2 The following tags frontmatter line is no longer read: "tags": "journal", See #3482
…by Obsidian 1.9.2 The following tags frontmatter line is no longer read: TAG: - value1 - value2 This means that getAllTags() and parseFrontMatterTags() do not see those tags. See #3482
… parsed differently by Obsidian 1.9.2 The following tags frontmatter line is no longer read: tags: single-value-single-line This means that getAllTags() and parseFrontMatterTags() do not see those tags. See #3482
…arsed differently by Obsidian 1.9.2 The following tags frontmatter line is no longer read: tags: value-1-of-2-on-one-line, value-2-of-2-on-one-line This means that getAllTags() and parseFrontMatterTags() do not see those tag values. See #3482
…some 1.9.x versions'
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
scope: documentation
Improvements or additions to documentation
scope: frontmatter
Anything to do with YAML frontmatter, also known as Obsidian properties
scope: parsing markdown
See also 'scope: global filter'
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Types of changes
Changes visible to users:
docs
- improvements to any documentation content for users)vault
- improvements to the Tasks-Demo sample vault)Internal changes:
test
- additions and improvements to unit tests and the smoke tests)Description
In addressing #3482 I've learned a bit more about how Obsidian 1.9.2 has changed its reading of properties
tags
,aliases
andcssclasses
properties - and the now un-supportedtag
,alias
,cssclass
properties.I've tried to write up a systematic way for others to update any affected notes in their vaults.
The new page will be published at:
https://publish.obsidian.md/tasks/Support+and+Help/Missing+tags,+aliases+and+cssclasses+in+Obsidian+some+1.9.x+versions
Motivation and Context
Fix #3482:
tags
andaliases
#3482How has this been tested?
In the test vault.
Checklist
yarn run lint
.Terms