Open
Conversation
See PKM-er#265 for how to find this fix.
Draft
|
Is there a reason blocking this from being merged? |
|
Looks like its semi-abandoned. Nothing being merged since 2023... |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
See this comment for how to find this fix and replace it in the Obsidian plugin.
This should close #202 and close #265 as well. Omitting this splitting actually lets the field be parsed correctly into a full date which Obsidian has no problem parsing on its own.
Please let me know if there's anything else that should be considered for this and I'd be happy to add it.