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

FR: Option to add/update file creation date only if doesn't already exist in yaml (YAML Timestamp option). #353

Closed
sessionsdev opened this issue Aug 15, 2022 · 5 comments · Fixed by #623
Assignees
Labels
rule suggestion Suggestion to add or edit a rule yaml YAML related issues or features

Comments

@sessionsdev
Copy link

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.

@sessionsdev sessionsdev added the rule suggestion Suggestion to add or edit a rule label Aug 15, 2022
@pjkaufman
Copy link
Collaborator

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.

@pjkaufman
Copy link
Collaborator

The option should be feasible to add. But I will caution that it may not fix all scenarios in question.

@pjkaufman pjkaufman added the yaml YAML related issues or features label Aug 16, 2022
@pjkaufman pjkaufman moved this to Backlog in Obsidian Linter Sep 17, 2022
@anatexis
Copy link

anatexis commented Jan 7, 2023

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.

@pjkaufman
Copy link
Collaborator

This is related to #621 which I believe I have a fix for.

@pjkaufman
Copy link
Collaborator

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
rule suggestion Suggestion to add or edit a rule yaml YAML related issues or features
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants