Complex JS Backend stuff

[TheOneValen]

Hi!

I would like do do something more complicated in the backend using the custom request handler (I would like to mimic a bookmark sync api, so I can sync bookmarks to trilium). There are a few libraries I have to use to make it feasable. I am not a JS expert (I did some Typescript).

I tried to put a library (lzutf8) into a backend script js note. Then in the parent node I tried to include it with require. Is this how it supposed to work? I do not get an error on the require but the lib does not seem to work. Sorry if I miss some basic stuff here....

Thanks!

[zadam]

Then in the parent node I tried to include it with require. Is this how it supposed to work? I do not get an error on the require but the lib does not seem to work. Sorry if I miss some basic stuff here....

Hi, yes, it's supposed to work like that. Trilium tries to emulate Common JS modules, but I think that not all libraries will work.

It's best to try to avoid dependencies like that.

[TheOneValen]

Thanks! My POC for decrypting the bookmarks (I try to re-implement xbrowsersync) worked by putting the lib into the parent note. Resulting in a very big note (just for some tiny part of the implementation). Big notes seem to load quite slowly, is that a known issue? What is the best practice here? Code in another app c&p into trilium? How can I debug my script? Any way I can write into the backend log?

[TheOneValen]

Yes, very curius, embedding it into the script works, require on a "sub" script does not.

[zadam]

Thanks for the library, I checked how it detects common.js and fixed the responsible code in Trilium so this now works (on master):

var lz = require('lzutf8');

var output = lz.compress("test");

Big notes seem to load quite slowly, is that a known issue?

Yes, but there's not much which can be done about it.

What is the best practice here? Code in another app c&p into trilium?

The best practice it keep the notes short, but that's not helpful in this scenario. But there's this which automates the re-upload into trilium:

How can I debug my script? Any way I can write into the backend log?

Yes - api.log() will write into the backend log:

[TheOneValen]

Hi. utcDateModified on a note seems to give me the creation datetime everytime. So does dateModified. Am I doing something wrong or is this a bug? @zadam

[TheOneValen]

Hi, the problem you're running again is that in some ways there are two separate entities "Note" and "NoteContents" which have separate dateModified, but this complexity is hidden on UI. If you want notecontent's datemodified, you can call note.getContentMetadata() (on backend API).

Similar problem happens with runOnNoteChange - this works only with the note properties and not with content. I've just added a separate event runOnNoteContentChange to master for this purpose.

I installed 58.4 but it does not seem to work. Is this correct: I put the relation on the note which content change I want to "watch". The script note does not get triggered. Am I missing something?

[zadam]

@TheOneValen yes, sounds correct. I just tested it and it seems to work for me. Just to be sure, is it a JS backend note? All the events work only for backend scripts.

[TheOneValen]

yes so it is like that:

js backend web script modifies text note via a web hook thingy
text note has the event relation to another js backend script decode
decode then decodes text to another note json
json has another event relation to another js backend script sync
sync reads json and does stuff

The modification web does works fine, but not event decode is triggered.

triggering decode then sync manually does work, but is very inconvenient.

[zadam]

I see, I didn't know the change was triggered from a script and tested on an UI. I could reproduce and fix the issue - the event was fired from a service layer and thus direct change from note.setContent() did not fire it. Will be in the next patch release.

[TheOneValen]

It works like a charm! Thank you! I'll clean up my stuff and put it into show and tell as soon as i am able :)