How to refresh after updating contents of current note?

[kylrth]

I'm writing a plugin that modifies the contents of the current note. In testing, I have to click on a different note and then click back in order to see the changes. How do I force the view to update when the note's contents updates?

I'm using the data API:

await joplin.data.put(['notes', note.id], null, { body: newBody });

I see this has been asked already (I can't include links but search "need to refresh my notes manually") with no reply.

For my use case, it's fine to just insert at the cursor, so that's what I'm doing now (following a post I found by searching "modifying note content"). It still seems like the data API should cause the view to refresh if the current note's body is updated.

[ajay]

Not knowing anything about plugin development, but - in general - the easiest way to see the "latest version" of a note is to select / view a different note, and then go back to the note you have changed.

[JackGruber]

I'm not sure if the whole thing has ever been discussed for put API ... I can't find anything at the moment.

@ajay

Not knowing anything about plugin development, but - in general - the easiest way to see the "latest version" of a note is to select / view a different note, and then go back to the note you have changed.

Sorry, but this is not a solution for a plugin!

As a reference how I have solved this in my plugins, if someone is looking for it

How to show the newest note after using data.put

I am trying to write a plugin,but meet a problem. I used await joplin.data.put(['notes', todoID], null, { body: "body note"}) to change the body of a note, but I could only see the old note after the code is executed. When I clicked another note and then clicked back to the note, the note body is the new one. How can I refresh the note after using joplin.data.put() command?

[kylrth]

Sounds like this is an issue for many. I wonder if a Joplin dev could weigh in?