-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
(Bug report) Frontend API in 0.61 can no longer get a note's creation date #4232
Comments
Somewhat related: There's also not an equivalent for the I believe these were the most recent date of either the note's modified date or the content's modified date. The combined date is shown by the Note Info widget: trilium/src/public/app/widgets/ribbon_widgets/note_info_widget.js Lines 130 to 132 in 72b2a6e
Scripts can currently only get the blob's modified date which is not necessarily the same. Preferably when showing the date modified, I would want it to be the same one shown under Note Info. Either |
Indeed, but these "combined" dates are no longer necessary. The note storage approach was redesigned in 0.61, and because of that |
Awesome, thanks! |
Trilium Version
0.61.5-beta
What operating system are you using?
Windows
What is your setup?
Local + server sync
Operating System Version
Windows 10 22H2
Description
Before 0.61, the Frontend API had a
note.getNoteComplement
method which returned an object that included the note's creation date (dateCreated
andutcDateCreated
):As of 0.61,
note.getNoteComplement
has been deprecated in favour ofnote.getBlob
, both of which return anFBlob
object. ButFBlob
does not have a creation date.There currently doesn't seem to be a (documented) way to obtain a note's creation date using the Frontend API. This breaks a use case where scripts could obtain and use the creation dates of notes (mabeyj/trilium-collection-views#41).
Can
dateCreated
andutcDateCreated
for notes be made available somewhere in the Frontend API?Error logs
No response
The text was updated successfully, but these errors were encountered: