Allow override for createdAt and updatedAt properties #254
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
Description
Resolves: #252
This stems from the linked issue, but I did also thought about this a while ago when considering to retain the datetime if I'm migrating the posts to nuxt/content.
Checklist:
I have mentioned that the
createdAt
andupdatedAt
properties can be overrided in the docs over here.I'm not particular sure how we can add tests for this since the original createdAt & updatedAt of the files can be different if I make a new fork of the repo. With that said, I did do some tests myself and here are the test results:
Note that my timezone is UTC +8, so there's 8 hours offset for the results with time.