Skip to content
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

joplin.workspace.onNoteChange not consistently called when a todo state is changed #11751

Closed
Supremekirb opened this issue Jan 29, 2025 · 3 comments
Labels
bug It's a bug stale An issue that hasn't been active for a while...

Comments

@Supremekirb
Copy link

Operating system

Linux

Joplin version

3.2.12

Desktop version info

No response

Current behaviour

joplin.workspace.onNoteChange is called when a todo's completion state is changed, but only if that todo is the current note.

Expected behaviour

joplin.workspace.onNoteChange should be called when a todo's completion state is changed even if it isn't the current note.

Logs

No response

@Supremekirb Supremekirb added the bug It's a bug label Jan 29, 2025
@Supremekirb Supremekirb changed the title joplin.workspace.onNoteChange not consistently called when a todo state is change joplin.workspace.onNoteChange not consistently called when a todo state is changed Jan 29, 2025
@laurent22
Copy link
Owner

That's by design - joplin.workspace is only for the currently opened note.

You may be able to use the data API /events endpoint for this, but it won't be real time. You would have to poll it at regular intervals.

https://joplinapp.org/help/api/references/rest_api/#events

Copy link
Contributor

github-actions bot commented Mar 6, 2025

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? If you require support or are requesting an enhancement or feature then please create a topic on the Joplin forum. This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

@github-actions github-actions bot added the stale An issue that hasn't been active for a while... label Mar 6, 2025
Copy link
Contributor

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, feel free to create a new issue with up-to-date information.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug It's a bug stale An issue that hasn't been active for a while...
Projects
None yet
Development

No branches or pull requests

2 participants