Markdown content front matter, use createdAt and updatedAt like Nuxt does #69
Conversation
This file contains 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
renoirb
force-pushed
the
chore-front-matter-createdAt
branch
2 times, most recently
from
4db9fc3 to
5ade348
Compare
renoirb
force-pushed
the
chore-front-matter-createdAt
branch
from
5ade348 to
e1c6257
Compare
renoirb
force-pushed
the
chore-front-matter-createdAt
branch
from
e1c6257 to
edbbc19
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Because the fact that I want to use Obsidian to edit markdown files doesn't require me to have to use 'updated' and 'created' front matter to be kept up to date by Obsidian for me, versus the weight to handle Nuxt' page publication.