fix: Prevent multiple executions of db.onChanged callback#92
Open
braladin wants to merge 1 commit intosawhney17:mainfrom
Open
fix: Prevent multiple executions of db.onChanged callback#92braladin wants to merge 1 commit intosawhney17:mainfrom
braladin wants to merge 1 commit intosawhney17:mainfrom
Conversation
When we change a block, multiple events get triggered and logseq.DB.onChanged gets called multiple (3) times. This commit adds a guard clause to prevent executing the callback function multiple times.
7 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Issue
When we change a block, logseq.DB.onChanged gets called multiple (3) times.
Solution
This commit adds a guard clause to prevent executing the callback function multiple times for a single block change.