-
Notifications
You must be signed in to change notification settings - Fork 86
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
FR: Option to add/update file creation date only if doesn't already exist in yaml (YAML Timestamp option). #353
Comments
I don't recommend using date created across file systems. It is not designed for such use as it only knows about the current one and will try to make it work with that value. |
The option should be feasible to add. But I will caution that it may not fix all scenarios in question. |
It would be great if it would be added (again). In an earlier version of Linter it just updated the modified date. This was really useful for me because I imported a large number of notes from another software and I could manually modify the creation time and it didn't change afterwards. |
This is related to #621 which I believe I have a fix for. |
The change for this should now be on master and go out with the next release. Please let us know if that is not the case. |
I use obsidian and sync across several devices. When linting the file on any device, it updates the file creation time to the local system file creation time. For me, this limits the usefulness of recording the file creation date in the frontmatter.
Describe the Solution You'd Like
A toggle option to only write the file creation date if the key does not exist yet.
The text was updated successfully, but these errors were encountered: