fix(obsidian-1.9.0): use checkCallback instead of callback #1315
+6
−6
Conversation
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
Collaborator
|
This looks fine to me and looks to work. Thanks for taking a look and fixing this @kdnk . |
baodrate
reviewed
May 27, 2025
Comment on lines
+325
to
326
| saveCommandDefinition.checkCallback = () => { | ||
| this.originalSaveCallback(); |
There was a problem hiding this comment.
Per the api docs, shouldn't this be: ?
Suggested change
| saveCommandDefinition.checkCallback = () => { | |
| this.originalSaveCallback(); | |
| saveCommandDefinition.checkCallback = (checking: boolean) => { | |
| this.originalSaveCallback(checking); |
likewise, this.runLinterEditor below should be wrapped with if (!checking) { ... }
Contributor
Author
There was a problem hiding this comment.
@baodrate
Thank you! Right. I'll create another PR.
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Fix: #1314